commit_msg
stringlengths 1
24.2k
| commit_hash
stringlengths 2
84
⌀ | project
stringlengths 2
40
| source
stringclasses 4
values | labels
int64 0
1
| repo_url
stringlengths 26
70
⌀ | commit_url
stringlengths 74
118
⌀ | commit_date
stringlengths 25
25
⌀ |
|---|---|---|---|---|---|---|---|
i386: kvm: kvm_arch_get_supported_cpuid: move R_EDX hack outside of for loop
The for loop will become a separate function, so clean it up so it can
become independent from the bit hacking for R_EDX.
No behavior change[1], just code movement.
[1] Well, only if the kernel returned CPUID leafs 1 or 0x80000001 as
unsupported, but there's no kernel version that does that.
Signed-off-by: Eduardo Habkost <[email protected]>
Signed-off-by: Marcelo Tosatti <[email protected]>
|
7b46e5ce81d5107927685e7645b1bd39a1e1cd63
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7b46e5ce81d5107927685e7645b1bd39a1e1cd63
|
2012-10-30 23:39:45-02:00
|
qapi: do not protect enum values from namespace pollution
Enum values are always preceded by the uppercase name of the enum, so
they do not conflict with reserved words.
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Luiz Capitulino <[email protected]>
|
eda50a656f52a5172fa8a95f7b217565b90d413e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/eda50a656f52a5172fa8a95f7b217565b90d413e
|
2012-09-26 10:45:02-03:00
|
target-i386: Allow tsc-frequency to be larger then 2.147G
The check using INT_MAX (2147483647) is wrong in this case.
Signed-off-by: Fred Oliveira <[email protected]>
Signed-off-by: Don Slutz <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
2e84849aa2cc7f220d3b3668f5f7e3c57bb1b590
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/2e84849aa2cc7f220d3b3668f5f7e3c57bb1b590
|
2012-09-23 07:11:27+01:00
|
qxl/update_area_io: guest_bug on invalid parameters
Signed-off-by: Alon Levy <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
|
511b13e2c9b426b3c56060909693de5097f0b496
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/511b13e2c9b426b3c56060909693de5097f0b496
|
2012-09-05 17:11:55+02:00
|
Revert "i8259: add -no-spurious-interrupt-hack option"
This reverts commit f278d4947fff814dcde2ef2acad36d172ff8be35.
Signed-off-by: malc <[email protected]>
|
4f213879f3cc695644cfd8bf603495e7316c78f6
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4f213879f3cc695644cfd8bf603495e7316c78f6
|
2012-08-27 18:33:12+04:00
|
pseries: Use new method to correct reset sequence
A number of things need to occur during reset of the PAPR
paravirtualized platform in a specific order. For example, the hash
table needs to be cleared before the CPUs are reset, so that they
initialize their register state correctly, and the CPUs need to have
their main reset called before we set up the entry point state on the
boot cpu. We also need to have the main qdev reset happen before the
creation and installation of the device tree for the new boot, because
we need the state of the devices settled to correctly construct the
device tree.
We currently do the pseries once-per-reset initializations done from a
reset handler. However we can't adequately control when this handler
is called during the reset - in particular we can't guarantee it
happens after all the qdev resets (since qdevs might be registered
after the machine init function has executed).
This patch uses the new QEMUMachine reset method to to fix this
problem, ensuring the various order dependent reset steps happen in
the correct order.
Signed-off-by: David Gibson <[email protected]>
Reviewed-by: Andreas Färber <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
|
c8787ad477f3be5a971b877dcb1bae5752c5796a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c8787ad477f3be5a971b877dcb1bae5752c5796a
|
2012-10-04 15:54:17+02:00
|
pseries: added allocator for a block of IRQs
The patch adds a simple helper which allocates a consecutive sequence
of IRQs calling spapr_allocate_irq for each and checks that allocated
IRQs go consequently.
The patch is required for upcoming support of MSI/MSIX on POWER.
Signed-off-by: Alexey Kardashevskiy <[email protected]>
Signed-off-by: David Gibson <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
|
f4b9523ba6388f6f951933de3f9a76e2e9ea2ede
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f4b9523ba6388f6f951933de3f9a76e2e9ea2ede
|
2012-08-15 19:43:16+02:00
|
hmp: hmp_cont(): don't rely on QERR_DEVICE_ENCRYPTED
This commit changes hmp_cont() to loop through all block devices
and proactively set an encryption key for any encrypted device
missing a key.
This change is needed because QERR_DEVICE_ENCRYPTED is going to be
dropped by a future commit.
Signed-off-by: Luiz Capitulino <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
|
8b7f6fbbdc5545f749864fdf295f2fae14c7ef0a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/8b7f6fbbdc5545f749864fdf295f2fae14c7ef0a
|
2012-08-13 13:20:12-03:00
|
configure: Fix xen probe with Xen 4.2 and later
The xs.h header is now deprecated and produces a warning. This prevents the
configure script from enabling Xen with xen-unstable whom will become 4.2. As
this header is not anymore common to every version of Xen, we just remove it
from the early probe for Xen.
Signed-off-by: Anthony PERARD <[email protected]>
Acked-by: Stefano Stabellini <[email protected]>
|
f6ccf1f45385c33ec0ea0463cdb0b1fba3bd7178
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f6ccf1f45385c33ec0ea0463cdb0b1fba3bd7178
|
2012-08-01 13:42:44+00:00
|
qapi: add test case for deallocating traversal of incomplete structure
v3:
- new patch
Signed-off-by: Laszlo Ersek <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
d98150f0522890046b3cc699552a3c94d9645cb6
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/d98150f0522890046b3cc699552a3c94d9645cb6
|
2012-07-23 11:55:17+01:00
|
qemu-img check -r for repairing images
The QED block driver already provides the functionality to not only
detect inconsistencies in images, but also fix them. However, this
functionality cannot be manually invoked with qemu-img, but the
check happens only automatically during bdrv_open().
This adds a -r switch to qemu-img check that allows manual invocation
of an image repair.
Signed-off-by: Kevin Wolf <[email protected]>
|
4534ff5426afeeae5238ba10a696cafa9a0168ee
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4534ff5426afeeae5238ba10a696cafa9a0168ee
|
2012-06-15 14:03:42+02:00
|
Allow QEMUMachine to override reset sequencing
qemu_system_reset() function always performs the same basic actions on
all machines. This includes running all the reset handler hooks,
however the order in which these will run is not always easily predictable.
This patch splits the core of qemu_system_reset() - the invocation of
the reset handlers - out into a new qemu_devices_reset() function.
qemu_system_reset() will usually call qemu_devices_reset(), but that
can be now overriden by a new reset method in the QEMUMachine
structure.
Individual machines can use this reset method, if necessary, to
perform any extra, machine specific initializations which have to
occur before or after the bulk of the reset handlers. It's expected
that the method will call qemu_devices_reset() at some point, but if
the machine has really strange ordering requirements between devices
resets it could even override that with it's own reset sequence (with
great care, obviously).
For a specific example of when this might be needed: a number of
machines (but not PC) load images specified with -kernel or -initrd
directly into the machine RAM before booting the guest. This mostly
works at the moment, but to make this actually safe requires that this
load occurs after peripheral devices are reset - otherwise they could
have active DMAs in progress which would clobber the in memory images.
Some machines (notably pseries) also have other entry conditions which
need to be set up as the last thing before executing in guest space -
some of this could be considered "emulated firmware" in the sense that
the actions of the firmware are emulated directly by qemu rather than
by executing a firmware image within the guest. When the platform's
firmware to OS interface is sufficiently well specified, this saves
time both in implementing the "firmware" and executing it.
aliguori: don't unconditionally dereference current_machine
Reviewed-by: Andreas Färber <[email protected]>
Signed-off-by: David Gibson <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
be52202902d166e914d426c8e3d8976b25121b4d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/be52202902d166e914d426c8e3d8976b25121b4d
|
2012-08-16 13:41:17-05:00
|
slirp: Avoid redefining MAX_TCPOPTLEN
MAX_TCPOPTLEN is being defined as 32. Darwin already has it as 40,
causing a warning. The value is only used to declare an array,
into which currently 4 bytes are written at most.
Therefore always override MAX_TCPOPTLEN for now.
Suggested-by: Jan Kiszka <[email protected]>
Reviewed-by: Stefan Weil <[email protected]>
Signed-off-by: Andreas Färber <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
|
917cfc1f266b554ea9ab4d958fa048bd27bce58f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/917cfc1f266b554ea9ab4d958fa048bd27bce58f
|
2012-05-28 22:44:27+02:00
|
tests: Add rtc-test (fix test regression)
Commit 93e9eb6808c886f5f1c903b7ced1eed65de2ba39 added fdc-test,
but accidentally removed rtc-test because check-qtest-i386-y was
not enhanced but set twice.
This patch adds rtc-test again (and sorts both tests alphabetically).
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
fba0c40bb7c30211b13903df8632d4acea9834db
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fba0c40bb7c30211b13903df8632d4acea9834db
|
2012-05-21 15:31:06-05:00
|
qapi: introduce OptsVisitor
This visitor supports parsing
-option [type=]discriminator[,optarg1=val1][,optarg2=val2][,...]
style QemuOpts objects into "native" C structures. After defining the type
tree in the qapi schema (see below), a root type traversal with this
visitor linked to the underlying QemuOpts object will build the "native" C
representation of the option.
The type tree in the schema, corresponding to an option with a
discriminator, must have the following structure:
struct
scalar member for non-discriminated optarg 1 [*]
list for repeating non-discriminated optarg 2 [*]
wrapper struct
single scalar member
union
struct for discriminator case 1
scalar member for optarg 3 [*]
list for repeating optarg 4 [*]
wrapper struct
single scalar member
scalar member for optarg 5 [*]
struct for discriminator case 2
...
The "type" optarg name is fixed for the discriminator role. Its schema
representation is "union of structures", and each discriminator value must
correspond to a member name in the union.
If the option takes no "type" descriminator, then the type subtree rooted
at the union must be absent from the schema (including the union itself).
Optarg values can be of scalar types str / bool / integers / size.
Members marked with [*] may be defined as optional in the schema,
describing an optional optarg.
Repeating an optarg is supported; its schema representation must be "list
of structure with single mandatory scalar member". If an optarg is not
described as repeating in the schema (ie. it is defined as a scalar field
instead of a list), its last occurrence will take effect. Ordering between
differently named optargs is not preserved.
A mandatory list (or an optional one which is reported to be available),
corresponding to a repeating optarg, has at least one element after
successful parsing.
v1->v2:
- Update opts_type_size() prototype to uint64_t.
- Add opts_type_uint64() for options needing the full uint64_t range.
(Internals could be extracted to "cutils.c".)
- Allow negative values in opts_type_int().
- Rebase to nested Makefiles.
v2->v3:
- Factor opts_visitor_insert() out of opts_start_struct() and call it
separately for opts_root->id if there's any.
- Don't require non-negative values in opts_type_int()'s error message.
- g_malloc0() may return NULL for zero-sized requests. Support empty
structures by requesting 1 byte for them instead.
Signed-off-by: Laszlo Ersek <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
eb7ee2cbebe4ac9e687d5fb3c104f0220d26cdfc
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/eb7ee2cbebe4ac9e687d5fb3c104f0220d26cdfc
|
2012-07-23 11:55:17+01:00
|
Fixes related to processing of qemu's -numa option
The -numa option to qemu is used to create [fake] numa nodes
and expose them to the guest OS instance.
There are a couple of issues with the -numa option:
a) Max VCPU's that can be specified for a guest while using
the qemu's -numa option is 64. Due to a typecasting issue
when the number of VCPUs is > 32 the VCPUs don't show up
under the specified [fake] numa nodes.
b) KVM currently has support for 160VCPUs per guest. The
qemu's -numa option has only support for upto 64VCPUs
per guest.
This patch addresses these two issues.
Below are examples of (a) and (b)
a) >32 VCPUs are specified with the -numa option:
/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
71:01:01 \
-net tap,ifname=tap0,script=no,downscript=no \
-vnc :4
...
Upstream qemu :
--------------
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info numa
6 nodes
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 32 33 34 35 36 37 38 39 40 41
node 0 size: 131072 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19 42 43 44 45 46 47 48 49 50 51
node 1 size: 131072 MB
node 2 cpus: 20 21 22 23 24 25 26 27 28 29 52 53 54 55 56 57 58 59
node 2 size: 131072 MB
node 3 cpus: 30
node 3 size: 131072 MB
node 4 cpus:
node 4 size: 131072 MB
node 5 cpus: 31
node 5 size: 131072 MB
With the patch applied :
-----------------------
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info numa
6 nodes
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 0 size: 131072 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
node 1 size: 131072 MB
node 2 cpus: 20 21 22 23 24 25 26 27 28 29
node 2 size: 131072 MB
node 3 cpus: 30 31 32 33 34 35 36 37 38 39
node 3 size: 131072 MB
node 4 cpus: 40 41 42 43 44 45 46 47 48 49
node 4 size: 131072 MB
node 5 cpus: 50 51 52 53 54 55 56 57 58 59
node 5 size: 131072 MB
b) >64 VCPUs specified with -numa option:
/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
-cpu Westmere,+rdtscp,+pdpe1gb,+dca,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+d-vnc :4
...
Upstream qemu :
--------------
only 63 CPUs in NUMA mode supported.
only 64 CPUs in NUMA mode supported.
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info numa
8 nodes
node 0 cpus: 6 7 8 9 38 39 40 41 70 71 72 73
node 0 size: 65536 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19 42 43 44 45 46 47 48 49 50 51 74 75 76 77 78 79
node 1 size: 65536 MB
node 2 cpus: 20 21 22 23 24 25 26 27 28 29 52 53 54 55 56 57 58 59 60 61
node 2 size: 65536 MB
node 3 cpus: 30 62
node 3 size: 65536 MB
node 4 cpus:
node 4 size: 65536 MB
node 5 cpus:
node 5 size: 65536 MB
node 6 cpus: 31 63
node 6 size: 65536 MB
node 7 cpus: 0 1 2 3 4 5 32 33 34 35 36 37 64 65 66 67 68 69
node 7 size: 65536 MB
With the patch applied :
-----------------------
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info numa
8 nodes
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 0 size: 65536 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
node 1 size: 65536 MB
node 2 cpus: 20 21 22 23 24 25 26 27 28 29
node 2 size: 65536 MB
node 3 cpus: 30 31 32 33 34 35 36 37 38 39
node 3 size: 65536 MB
node 4 cpus: 40 41 42 43 44 45 46 47 48 49
node 4 size: 65536 MB
node 5 cpus: 50 51 52 53 54 55 56 57 58 59
node 5 size: 65536 MB
node 6 cpus: 60 61 62 63 64 65 66 67 68 69
node 6 size: 65536 MB
node 7 cpus: 70 71 72 73 74 75 76 77 78 79
Signed-off-by: Chegu Vinod <[email protected]>, Jim Hull <[email protected]>, Craig Hada <[email protected]>
Tested-by: Eduardo Habkost <[email protected]>
Reviewed-by: Eduardo Habkost <[email protected]>
Signed-off-by: Blue Swirl <[email protected]>
|
ee785fed5dd035d4b12142cacec6d3c344426dec
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ee785fed5dd035d4b12142cacec6d3c344426dec
|
2012-08-04 13:23:58+00:00
|
qemu-ga: guest-suspend-disk: don't emit a success response
Today, qemu-ga may not be able to emit a success response when
guest-suspend-disk completes. This happens because the VM may
vanish before qemu-ga is able to emit a response.
This semantic is a bit confusing, as it's not clear for clients if
they should wait for a response or how they should check for success.
This commit solves that problem by changing guest-suspend-disk to
never emit a success response and suggests in the documentation
what clients could do to check for success.
Signed-off-by: Luiz Capitulino <[email protected]>
Signed-off-by: Michael Roth <[email protected]>
|
c6fcc10ab31d22e93eb169c451025ac9636ec84b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c6fcc10ab31d22e93eb169c451025ac9636ec84b
|
2012-05-15 09:15:16-05:00
|
runstate: introduce suspended state
QEMU enters in this state when the guest suspends to ram (S3).
This is important so that HMP users and QMP clients can know that
the guest is suspended. QMP also has an event for this, but events
are not reliable and are limited (ie. a client can connect to QEMU
after the event has been emitted).
Having a different state for S3 brings a new issue, though. Every
device that doesn't run when the VM is stopped but wants to run
when the VM is suspended has to check for RUN_STATE_SUSPENDED
explicitly. This is the case for the keyboard and mouse devices,
for example.
Signed-off-by: Luiz Capitulino <[email protected]>
Acked-by: Gerd Hoffmann <[email protected]>
|
ad02b96ad86baf6dd72a43b04876b2d6ea957112
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ad02b96ad86baf6dd72a43b04876b2d6ea957112
|
2012-05-08 14:30:09-03:00
|
usb-redir: An interface count of 0 is a valid value
An interface-count of 0 happens when a device is in unconfigured state when
it gets redirected. So we should not use 0 to detect not having received
interface info from our peer.
Signed-off-by: Hans de Goede <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
|
1510168e273a12a56e3bd4488b4b2904f5138e09
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1510168e273a12a56e3bd4488b4b2904f5138e09
|
2012-04-26 12:21:17+02:00
|
target-arm: Move OMAP cp15_i_{max,min} reset to cpu_state_reset
Move the OMAP-specific cp15_i_{max,min} reset to cpu_state_reset;
since these registers are only accessible on CPUs with the
OMAPCP feature set there's no need to guard this reset with
either a CPUID or feature bit check.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Andreas Färber <[email protected]>
|
8092d2f031e70eb2664d5fa1d9ed00ef1113ee71
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/8092d2f031e70eb2664d5fa1d9ed00ef1113ee71
|
2012-04-21 18:12:27+00:00
|
usb-ehci: Ensure frindex writes leave a valid frindex value
frindex is a 14 bits counter, so bits 31-14 should always be 0, and
after the commit titled "usb-ehci: frindex always is a 14 bits counter"
we rely on frindex always being a multiple of 8. I've not seen this in
practice, but theoretically a guest can write a value >= 0x4000 or a value
which is not a multiple of 8 value to frindex, this patch ensures that
things will still work when that happens.
Signed-off-by: Hans de Goede <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
|
8a771f77e2abfb81f1f33a986810c16ecae54ca7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/8a771f77e2abfb81f1f33a986810c16ecae54ca7
|
2012-04-26 12:21:15+02:00
|
qdev: give all devices a canonical path
A strong limitation of QOM right now is that unconverted ports
(e.g. all...) do not give a canonical path to devices that are
part of the board. This in turn makes it impossible to replace
PROP_PTR with a QOM link for example.
Reviewed-by: Anthony Liguori <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
da57febfed7bad11be79f047b59719c38abd0712
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/da57febfed7bad11be79f047b59719c38abd0712
|
2012-04-02 15:04:15-05:00
|
spice: fix broken initialization
Commit 1b71f7c14fab6f00c2680d4489fbee7baf796e4f moved MODULE_INIT_QOM to
way before MODULE_INIT_MACHINE, thereby breaking assumptions made in
spice-core.c which registered both a type initializer and a machine
intializer.
This fix removes the type registration, and replaces it with calling
qemu_spice_init in vl.c after command line parsing (second pass) is
done, and after timers are armed, required by spice server.
Signed-off-by: Alon Levy <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
|
ad1be89948f88e89708b04ccd782456ccec3a6f0
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ad1be89948f88e89708b04ccd782456ccec3a6f0
|
2012-03-19 13:12:19+01:00
|
pci: fix bridge IO/BASE
commit 5caef97a16010f818ea8b950e2ee24ba876643ad introduced
a regression: we do not make IO base/limit upper 16
bit registers writeable, so we should report a 16 bit
IO range type, not a 32 bit one.
Note that PCI_PREF_RANGE_TYPE_32 is 0x0, but PCI_IO_RANGE_TYPE_32 is 0x1.
In particular, this broke sparc64.
Note: this just reverts to behaviour prior to the commit above.
Making PCI_IO_BASE_UPPER16 and PCI_IO_LIMIT_UPPER16
registers writeable should, and seems to, work just as well, but
as no system seems to actually be interested in 32 bit IO,
let's not make unnecessary changes.
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
68917102740d9aa96c8f3ed4b95eab9917e8c61b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/68917102740d9aa96c8f3ed4b95eab9917e8c61b
|
2012-03-16 00:41:39+02:00
|
qxl: remove flipped
Tested on linux and windows guests. For negative stride, qxl_flip copies
directly to vga->ds->surface->data, for positive it's reallocated to
share qxl->guest_primary.data
Signed-off-by: Alon Levy <[email protected]>
Signed-off-by: Gerd Hoffmann <[email protected]>
|
4c19ebb51dc0a59ff12d60844512816562a25047
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4c19ebb51dc0a59ff12d60844512816562a25047
|
2012-02-27 09:46:52+01:00
|
fdc: add CCR (Configuration Control Register) write register
DIR and CCR registers share the same address ; DIR is read-only
while CCR is write-only
CCR register is used to change media transfer rate, which will be
checked in following changes.
Signed-off-by: Hervé Poussineau <[email protected]>
Signed-off-by: Kevin Wolf <[email protected]>
|
a758f8f415985abc85be1da6d22f0590a74ca23d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a758f8f415985abc85be1da6d22f0590a74ca23d
|
2012-02-29 12:48:46+01:00
|
qom: accept any compatible type when setting a link property
Links had limited utility before as they only allowed a concrete type to be
specified. Now we can support abstract types and interfaces which means it's
now possible to have a link<PCIDevice>.
Signed-off-by: Anthony Liguori <[email protected]>
|
fe40e627c51e38922b64b02b6163aea4b6aad896
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fe40e627c51e38922b64b02b6163aea4b6aad896
|
2012-02-03 10:41:08-06:00
|
linux-user: fake /proc/self/maps
glibc's pthread_attr_getstack tries to find the stack range from
/proc/self/maps. Unfortunately, /proc is usually the host's /proc
which means linux-user guests see qemu's stack there.
Fake the file with a constructed maps entry that exposes the guest's
stack range.
Signed-off-by: Alexander Graf <[email protected]>
Signed-off-by: Riku Voipio <[email protected]>
|
36c08d498b8ea6995666b805d37c6bb14da66a97
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/36c08d498b8ea6995666b805d37c6bb14da66a97
|
2012-02-02 17:51:20+02:00
|
qdev: remove baked in notion of aliases (v2)
Limit them to the device_add functionality. Device aliases were a hack based
on the fact that virtio was modeled the wrong way. The mechanism for aliasing
is very limited in that only one alias can exist for any device.
We have to support it for the purposes of compatibility but we only need to
support it in device_add so restrict it to that piece of code.
Signed-off-by: Anthony Liguori <[email protected]>
---
v1 -> v2
- Use a table for aliases (Paolo)
|
6acbe4c6f18e7de00481ff30574262b58526de45
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6acbe4c6f18e7de00481ff30574262b58526de45
|
2012-02-03 10:41:07-06:00
|
do not chdir(/) in qemu-nbd before opening all files
When qemu-nbd becomes a daemon it calls daemon(3) with
nochdir=0, so daemon(3) changes current directory to /.
But at this time, qemu-nbd did not open any user-specified
files yet, so by changing current directory, all non-absolute
paths becomes wrong. The solution is to pass nochdir=1 to
daemon(3) function, and to chdir("/") after all init has
been performed, before entering the main loop, -- just like
a good daemon should do.
This patch is applicable for -stable.
Signed-off-by: Michael Tokarev <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
|
9faf31b68f049ca6432a1ef086a76344ff2a2357
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/9faf31b68f049ca6432a1ef086a76344ff2a2357
|
2012-02-17 12:41:48+01:00
|
PPC: booke206: allow NULL raddr in ppcmas_tlb_check
We might want to call the tlb check function without actually caring about
the real address resolution. Check if we really should write the value
back.
Signed-off-by: Alexander Graf <[email protected]>
|
ffba87862b37f1d7762370c8d31b09f6e359ff09
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ffba87862b37f1d7762370c8d31b09f6e359ff09
|
2012-02-02 02:47:45+01:00
|
virtfs-proxy-helper: Add missing printf format attribute
Every function with printf like arguments must have it
(see file HACKING), so add it.
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
c5c7d3f0a79a977955e9df436cf9ca17269b8783
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c5c7d3f0a79a977955e9df436cf9ca17269b8783
|
2012-01-13 10:37:00+00:00
|
hw/pl110.c: Add post-load hook to invalidate display
Add a post-load hook which invalidates the display. In particular, if we
don't do this and the display size we've just reloaded is larger than
the default then we will segfault trying to read off the end of the buffer.
Signed-off-by: Peter Maydell <[email protected]>
|
128939a954194e37bbe67d1b94abcba599d30d10
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/128939a954194e37bbe67d1b94abcba599d30d10
|
2012-01-04 10:32:16+00:00
|
xhci: Initial xHCI implementation
Based on the implementation from Hector Martin <[email protected]>
Hectors's implementation completely sidestepped the qemu usb system and
used libusb directly for usb device pass through. So I've ripped out
the libusb bits (or left them in disabled, as reference for further
coding) and hooked up the qemu subsystem instead. That work is not
complete yet though, partly due to limitations of the qemu usb
subsystem. Nevertheless I think it is better to continue development
in-tree, especially as the qemu usb bits need a bunch of improvements
too for decent usb 3.0 support.
Current state:
- usb-storage emulation should work ok.
- Devices which need constant polling (HID emulation like usb-tablet)
are known to not work.
- ISO xfers are not implemented yet.
- superspeed ports are not implemented yet.
- usb pass-through is completely untested so far.
Signed-off-by: Gerd Hoffmann <[email protected]>
|
62c6ae04cf4334ef2ab5ef04581394850f4ea714
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/62c6ae04cf4334ef2ab5ef04581394850f4ea714
|
2012-01-17 09:44:32+01:00
|
virtio-serial-bus: Ports are expected to implement 'have_data' callback
There's no need to check if ports can accept any incoming data from the
guest each time the guest sends data. Check if the port implements such
functionality during port initialisation.
Signed-off-by: Amit Shah <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
03ecd2c80a64d030a22fe67cc7a60f24e17ff211
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/03ecd2c80a64d030a22fe67cc7a60f24e17ff211
|
2011-12-21 15:00:29-06:00
|
exec_close(): return -errno on errors (v2)
All qemu_fclose() callers were already changed to accept any negative
value as error, so we now can change it to return -errno.
When the process exits with a non-zero exit code, we return -EIO to as a
fake errno value.
Changes v1 -> v2:
- Don't use "//" comments, to make checkpatch.pl happy
Signed-off-by: Eduardo Habkost <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
e375fe3472f6d64971d3bd8e10a3f159e72435a1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e375fe3472f6d64971d3bd8e10a3f159e72435a1
|
2011-12-12 11:47:20-06:00
|
configure: Pull linux-headers/asm symlink creation out of loop
Pull the creation of the linux-headers/asm symlink out of the loop
so we don't pointlessly delete and recreate it once for each target.
Also move the setting of the includes variable up so that it is
in the same place as the other code which sets this variable.
Signed-off-by: Peter Maydell <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
6efd751789896dd6ac05c12f5149bba29c12ccae
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6efd751789896dd6ac05c12f5149bba29c12ccae
|
2011-12-06 09:56:41+00:00
|
migrate_fd_cleanup: accept any negative qemu_fclose() value as error
Also, we now return the qemu_fclose() value unchanged to the caller. For
reference, the migrate_fd_cleanup() callers are the following:
- migrate_fd_completed(): any negative value is considered an
error, so the change is OK.
- migrate_fd_error(): doesn't check the migrate_fd_cleanup() return value
- migrate_fd_cancel(): doesn't check the migrate_fd_cleanup() return
value
Signed-off-by: Eduardo Habkost <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
a6d34a949c3546404d403bda61a5e37431b4a6ad
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a6d34a949c3546404d403bda61a5e37431b4a6ad
|
2011-12-12 11:47:19-06:00
|
add test-coroutine to checks
There is a "test-coroutine" which isn't in the list.
Add it so "make check" runs it too.
Signed-off-by: Gerd Hoffmann <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
695833bc8bbb9f1dbb0d7736cbe927863e1b40cd
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/695833bc8bbb9f1dbb0d7736cbe927863e1b40cd
|
2011-11-01 11:50:21-05:00
|
hw/9pfs: Use export flag for indicating security model
This helps to remove some of the structure members
Signed-off-by: Aneesh Kumar K.V <[email protected]>
|
b97400caef60ccfb0bc81c59f8bd824c43a0d6c8
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b97400caef60ccfb0bc81c59f8bd824c43a0d6c8
|
2011-10-15 15:30:27+05:30
|
hw/9pfs: Initialize rest of qid field to zero.
Since qid is allocated out of stack we need to intialize
the field to zero. Otherwise we will send wrong qid value
to client.
Signed-off-by: Aneesh Kumar K.V <[email protected]>
|
25427ec1437b63e335a30293b58d47b601373223
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/25427ec1437b63e335a30293b58d47b601373223
|
2011-09-09 14:45:55+05:30
|
pseries: Correct RAM size check for SLOF
The SLOF firmware used on the pseries machine needs a reasonable amount of
(guest) RAM in order to run, so we have a check in the machine init
function to check that this is available. However, SLOF runs in real mode
(MMU off) which means it can only actually access the RMA (Real Mode Area),
not all of RAM. In many cases the RMA is the same as all RAM, but when
running with Book3S HV KVM on PowerPC 970, the RMA must be especially
allocated to be (host) physically contiguous. In this case, the RMA size
is determined by what the host admin allocated at boot time, and will
usually be less than the whole guest RAM size.
This patch corrects the test to see if SLOF has enough memory for this
case.
In addition, more recent versions of SLOF that were committed earlier don't
need quite as much memory as earlier versions. Therefore, this patch also
reduces the amount of RAM we require to run SLOF.
Signed-off-by: David Gibson <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
|
92c93a816a8c04071264f9fb47cbc90a5e1ae5d8
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/92c93a816a8c04071264f9fb47cbc90a5e1ae5d8
|
2011-11-18 14:22:45+01:00
|
tcg-i386: Introduce limited deposit support
x86 cannot provide an optimized generic deposit implementation. But at
least for a few special cases, namely for writing bits 0..7, 8..15, and
0..15, versions using only a single instruction are feasible.
Introducing such limited support improves emulating 16-bit x86 code on
x86, but also rarer cases where 32-bit or 64-bit code accesses bytes or
words.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Blue Swirl <[email protected]>
|
a4773324b4bc5f15fe9b438e4cfff05e1ab16dfa
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a4773324b4bc5f15fe9b438e4cfff05e1ab16dfa
|
2011-10-01 06:42:46+00:00
|
linux-user: Add support for more VT ioctls
DirectFB-1.0 uses at least two of the four added ioctls, and the two
others were added for completeness. This patch was validated with the
program "vlock -all/-new".
Signed-off-by: Cédric VINCENT <[email protected]>
Cc: Riku Voipio <[email protected]>
Signed-off-by: Riku Voipio <[email protected]>
|
774750c088192112df1623610dc35d9e03983d49
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/774750c088192112df1623610dc35d9e03983d49
|
2011-07-11 16:10:49+03:00
|
memory: abstract cracking of write access ops into a function
The memory API automatically cracks large reads and writes into smaller
ones when needed. Factor out this mechanism, which is now duplicated between
memory reads and memory writes, into a function.
Signed-off-by: Avi Kivity <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
164a4dcd8d90a0db5ffa2174f693195744374418
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/164a4dcd8d90a0db5ffa2174f693195744374418
|
2011-08-21 18:27:33-05:00
|
usb-linux: Ensure devep != 0
So that we don't index endp_table with a negative index.
Signed-off-by: Gerd Hoffmann <[email protected]>
|
130314f83dc43fc3cc2f431d8cfa1595209673fe
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/130314f83dc43fc3cc2f431d8cfa1595209673fe
|
2011-06-14 12:56:49+02:00
|
pseries: Add device tree properties for VMX/VSX and DFP under kvm
Sufficiently recent PAPR specifications define properties "ibm,vmx"
and "ibm,dfp" on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the guest device tree and the guest
kernel will consequently assume they are not available. This is good,
because they are not supported under TCG. VMX is similar enough to
Altivec that it might be trivial to support, but VSX and DFP would
both require significant work to support in TCG.
However, when running under kvm on a host which supports these
instructions, there's no reason not to let the guest use them. This
patch, therefore, checks for the relevant support on the host CPU
and, if present, advertises them to the guest as well.
Signed-off-by: David Gibson <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
|
6659394fa1fa20aa640efa42c8fa5ee6994b6286
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6659394fa1fa20aa640efa42c8fa5ee6994b6286
|
2011-10-30 17:11:53+01:00
|
configure: Don't create symlinks to nonexistent targets
When we create the symlinks to source tree files, don't create them
if the file is not actually present in the source tree; this will
happen if the file is in a git submodule that wasn't checked out.
This also avoids the odd effect where an in-source-tree configure
will end up creating the missing file as a symlink to itself.
Signed-off-by: Peter Maydell <[email protected]>
Signed-off-by: Stefan Hajnoczi <[email protected]>
|
f9245e100f12f03338a4e7660879139defb4ae3e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f9245e100f12f03338a4e7660879139defb4ae3e
|
2011-06-24 09:13:36+01:00
|
virtio-pci.c: convert to PCIDEviceInfo to initialize ids
use PCIDeviceInfo to initialize ids.
Signed-off-by: Isaku Yamahata <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
e75ccf2c033fb0503d6cb7ddd0fd1dfa0aa4fc16
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e75ccf2c033fb0503d6cb7ddd0fd1dfa0aa4fc16
|
2011-06-12 10:33:38+03:00
|
hw/ac97.c: convert to PCIDeviceInfo to initialize ids
use PCIDeviceInfo to initialize ids.
Signed-off-by: Isaku Yamahata <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
0647b949a25f49090bfd0e83d8a90c18b4045bb7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0647b949a25f49090bfd0e83d8a90c18b4045bb7
|
2011-06-12 10:33:33+03:00
|
json-lexer: reset the lexer state on an invalid token
Signed-off-by: Michael Roth <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
529a0ef5f30e28a801d6527a3556adcaa4959669
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/529a0ef5f30e28a801d6527a3556adcaa4959669
|
2011-06-07 13:52:11-05:00
|
target-sparc: Do not check CPU_INTERRUPT_TIMER.
This bit is never set, therefore we should not read it either.
Signed-off-by: Richard Henderson <[email protected]>
Signed-off-by: Blue Swirl <[email protected]>
|
78aa29e4b8b0df716a25edc689cf24c7b5b424fe
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/78aa29e4b8b0df716a25edc689cf24c7b5b424fe
|
2011-05-08 16:55:23+00:00
|
kvm: Enable CPU SMEP feature
This patchset enables a new CPU feature SMEP (Supervisor Mode Execution
Protection) in QEMU-KVM. SMEP prevents kernel from executing code in application.
Updated Intel SDM describes this CPU feature. The document will be published soon.
SMEP is identified by CPUID leaf 7 EBX[7], which is 0 before. Get the right value by query KVM kernel module, so that guest can get SMEP through CPUID.
Signed-off-by: Yang, Wei <[email protected]>
Singed-off-by: Shan, Haitao <[email protected]>
Singed-off-by: Li, Xin <[email protected]>
Signed-off-by: Marcelo Tosatti <[email protected]>
|
f79116867ec80ed5d1d10043a3fd9ac8afd182c1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f79116867ec80ed5d1d10043a3fd9ac8afd182c1
|
2011-06-14 09:34:35-05:00
|
lm32: use lookup table for opcodes
Instead of a for loop use a faster lookup table.
Signed-off-by: Michael Walle <[email protected]>
Signed-off-by: Edgar E. Iglesias <[email protected]>
|
a5086f95421e43c7b9e1b28a111aae0be4848117
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a5086f95421e43c7b9e1b28a111aae0be4848117
|
2011-03-31 08:54:05+02:00
|
kvm: Drop return values from kvm_arch_pre/post_run
We do not check them, and the only arch with non-empty implementations
always returns 0 (this is also true for qemu-kvm).
Signed-off-by: Jan Kiszka <[email protected]>
CC: Alexander Graf <[email protected]>
Signed-off-by: Marcelo Tosatti <[email protected]>
|
7a39fe588251ba042c91bf23d53b0ba820bf964c
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7a39fe588251ba042c91bf23d53b0ba820bf964c
|
2011-02-14 12:39:46-02:00
|
Refactor thread retrieval and check
We have qemu_cpu_self and qemu_thread_self. The latter is retrieving the
current thread, the former is checking for equality (using CPUState). We
also have qemu_thread_equal which is only used like qemu_cpu_self.
This refactors the interfaces, creating qemu_cpu_is_self and
qemu_thread_is_self as well ass qemu_thread_get_self.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Blue Swirl <[email protected]>
|
b7680cb6078bd7294a3dd86473d3f2fdee991dd0
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b7680cb6078bd7294a3dd86473d3f2fdee991dd0
|
2011-03-13 14:44:21+00:00
|
Add checkpatch.pl from Linux kernel
Unchanged import from
http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-0.31
Signed-off-by: Blue Swirl <[email protected]>
|
1ec3f6f9abca4f4f73d7e8a74dd9b14c1f087a8e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1ec3f6f9abca4f4f73d7e8a74dd9b14c1f087a8e
|
2011-01-20 20:54:26+00:00
|
x86: Filter out garbage from segment flags dump
Only bits 8..23 of the segment flags contain valid data, so only dump
those when printing the CPU state.
Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
4058fd98fd7e9c476774717adbd49698dd273166
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4058fd98fd7e9c476774717adbd49698dd273166
|
2010-12-27 22:02:52+01:00
|
arm: basic support for ARMv4/ARMv4T emulation
Currently target-arm/ assumes at least ARMv5 core. Add support for
handling also ARMv4/ARMv4T. This changes the following instructions:
BX(v4T and later)
BKPT, BLX, CDP2, CLZ, LDC2, LDRD, MCRR, MCRR2, MRRC, MCRR, MRC2, MRRC,
MRRC2, PLD QADD, QDADD, QDSUB, QSUB, STRD, SMLAxy, SMLALxy, SMLAWxy,
SMULxy, SMULWxy, STC2 (v5 and later)
All instructions that are "v5TE and later" are also bound to just v5, as
that's how it was before.
This patch doesn _not_ include disabling of cp15 access and base-updated
data abort model (that will be required to emulate chips based on a
ARM7TDMI), because:
* no ARM7TDMI chips are currently emulated (or planned)
* those features aren't strictly necessary for my purposes (SA-1 core
emulation).
All v5 models are handled as they are v5T. Internally we still have a
check if the model is a v5(T) or v5TE, but as all emulated cores are
v5TE, those two cases are simply aliased (for now).
Patch is heavily based on patch by Filip Navara <[email protected]>
which in turn is based on work by Ulrich Hecht <[email protected]> and Vincent
Sanders <[email protected]>.
Signed-off-by: Dmitry Eremin-Solenikov <[email protected]>
Reviewed-by: Peter Maydell <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
be5e7a76010bd14d09f74504ed6368782e701888
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/be5e7a76010bd14d09f74504ed6368782e701888
|
2011-04-10 00:53:21+02:00
|
piix_pci: optimize set irq path
optimize irq routing in piix_pic.c which has been a TODO.
So far piix3 tracks each pirq level and checks whether a given pic pins is
asserted by seeing if each pirq is mapped into the pic pin.
This is independent on irq routing, but data path is on slow path.
Given that irq routing is rarely changed and asserting pic pins is on
data path, the path that asserts pic pins should be optimized and
chainging irq routing should be on slow path.
The new behavior with this patch series is to use bitmap which is addressed
by pirq and pic pins with a given irq routing.
When pirq is asserted, the bitmap is set and see if the pic pins is
asserted by checking the bitmaps.
When irq routing is changed, rebuild the bitmap and re-assert pic pins.
test:
- create VM with 4 e1000 nics in different pci slots
(i.e. fn=0 for each e1000)
Thus those e1000's INTA are connected to each PIRQ[A-D].
- run linux as guest and saw each devices triggers interrupt
by seeing /proc/interrupts. And then confirmed that each PIRQ[A-D]
surely asserted interrupts.
Because irq 10 and 11 are shared by 4 e1000's, it only one NIC is activated
with ifconfig ethN up/down when counting interrupts.
Cc: Michael S. Tsirkin <[email protected]>
Signed-off-by: Isaku Yamahata <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
ab431c283e7055bcd6fb622f212bb29e84a6a134
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ab431c283e7055bcd6fb622f212bb29e84a6a134
|
2011-04-01 15:54:03+03:00
|
virtio: fix up VQ checks
When migration triggers before a VQ is initialized,
base pa is 0 and last_used_index must be 0 too:
we don't have a ring to compare to.
Reported-by: Juan Quintela <[email protected]>
Tested-by: Juan Quintela <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
1abeb5a65d515f8a8a9cfc4a82342f731bd9321f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1abeb5a65d515f8a8a9cfc4a82342f731bd9321f
|
2010-11-24 17:25:44+02:00
|
Makefile: Fix check dependency breakage
Commit b152aa84d52882bb1846485a89baf13aa07c86bc broke the unit-tests
build, fix it.
Signed-off-by: Luiz Capitulino <[email protected]>
|
a6f9dd02f75685934ca52f038b6fcb38b661c283
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a6f9dd02f75685934ca52f038b6fcb38b661c283
|
2010-11-17 10:46:51-02:00
|
Makefile: Fix check dependency breakage
Commit b152aa84d52882bb1846485a89baf13aa07c86bc broke the unit-tests
build, fix it.
Signed-off-by: Luiz Capitulino <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
e71e00ed258202052570ae631536f4d7b65792fa
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e71e00ed258202052570ae631536f4d7b65792fa
|
2010-11-21 09:16:57-06:00
|
Use a Linux-style MAINTAINERS file
I make no claims that this is accurate or exhaustive but I think it's a
reasonable place to start.
As the file mentions, the purpose of this file is to give contributors
information about who they can go to with questions about a particular piece of
code or who they can ask for review.
If you sign up for a piece of code and indicate that it's Maintained or
Supported, please be prepared to be responsive to questions about that
subsystem.
Signed-off-by: Anthony Liguori <[email protected]>
---
v1 -> v2
- Sort alphabetically
- Copy in instructions from linux MAINTAINERS
- Fix entries based on review feedback
|
fd5d5c566af040be15f2cae1b14a47919974453d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fd5d5c566af040be15f2cae1b14a47919974453d
|
2010-11-30 14:38:55-06:00
|
multiboot: Prevent loading of x86_64 images
A via -kernel supplied x86_64 ELF image is being started in 32bit mode.
Detect and exit if a 64bit image has been supplied.
Signed-off-by: Adam Lackorzynski <[email protected]>
Acked-by: Alexander Graf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
9696846600cac4bd0dfd6835e45e69d25ec2b11e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/9696846600cac4bd0dfd6835e45e69d25ec2b11e
|
2010-11-16 09:31:18-06:00
|
qdev: reset qdev along with qdev tree
This patch changes the reset handling so that qdev has no knowledge of the
global system reset. Instead, a new bus/device level function is introduced
that allows all devices/buses on the bus/device to be reset using a depth
first transversal.
N.B. we have to expose the implicit system bus because we have various hacks
that result in an implicit system bus existing. Instead, we ought to have an
explicitly created system bus that we can trigger reset from. That's a topic
for a future patch though.
Signed-off-by: Anthony Liguori <[email protected]>
Signed-off-by: Isaku Yamahata <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
|
ec990eb622ad46df5ddcb1e94c418c271894d416
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ec990eb622ad46df5ddcb1e94c418c271894d416
|
2010-11-22 10:00:07+02:00
|
[virtio-9p] Ignore O_DIRECT hint from client.
The O_DIRECT flag imposes alignment restrictions on the length and address
of userspace buffers and the file offset of I/Os.
While VirtFS/9P has plans to implement O_DIRECT behavior on the server,
for now we will stick to a behavior like NFS by bypassing the page cache
only on the client. Server may still cache the I/O.
Signed-off-by: Venkateswararao Jujjuri <[email protected]>
|
0f8151cb75e09c9a7de24a37f22166e46a9eaf7b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0f8151cb75e09c9a7de24a37f22166e46a9eaf7b
|
2010-10-20 12:10:58-05:00
|
vnc: check fd before calling qemu_set_fd_handler2() in vnc_client_write()
Setting fd = -1 to qemu_set_fd_handler2() causes bus error at FD_SET
in main_loop_wait().
Signed-off-by: Yoshiaki Tamura <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
ac71103dc6b408775ae72067790ab367912f75ec
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ac71103dc6b408775ae72067790ab367912f75ec
|
2010-08-22 16:48:23-05:00
|
blkdebug: Fix set_state_opts definition
The list head was initialized to point to the wrong list, so all actions ended
up being handled as inject-error even if they were set-state in fact.
Signed-off-by: Kevin Wolf <[email protected]>
|
327cdad4163dcf3928472e0cdbf6b6b97c88670b
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/327cdad4163dcf3928472e0cdbf6b6b97c88670b
|
2010-07-02 13:18:02+02:00
|
[virtio-9p] This patch implements TLCREATE for 9p2000.L protocol.
SYNOPSIS
size[4] Tlcreate tag[2] fid[4] name[s] flags[4] mode[4] gid[4]
size[4] Rlcreate tag[2] qid[13] iounit[4]
DESCRIPTION
The Tlreate request asks the file server to create a new regular file with the
name supplied, in the directory (dir) represented by fid.
The mode argument specifies the permissions to use. New file is created with
the uid if the fid and with supplied gid.
The flags argument represent Linux access mode flags with which the caller
is requesting to open the file with. Protocol allows all the Linux access
modes but it is upto the server to allow/disallow any of these acess modes.
If the server doesn't support any of the access mode, it is expected to
return error.
To start with we will not restricit/limit any Linux flags on this server.
If needed, We can start restricting as we move forward with various use cases.
Signed-off-by: Venkateswararao Jujjuri <[email protected]>
|
c1568af597d71b2171c9b2ffffb336c2fdee205e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c1568af597d71b2171c9b2ffffb336c2fdee205e
|
2010-09-08 22:56:40+05:30
|
check-qdict: Introduce test for the new iteration API
Signed-off-by: Luiz Capitulino <[email protected]>
|
d02c6bd428ddebd11c6e8f1bf13013b97c397628
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/d02c6bd428ddebd11c6e8f1bf13013b97c397628
|
2010-07-01 14:27:13-03:00
|
QMP: New argument checker (second part)
This commit introduces the second (and last) part of QMP's new
argument checker.
The job is done by check_client_args_type(), it iterates over
the client's argument qdict and for for each argument it checks
if it exists and if its type is valid.
It's important to observe the following changes from the existing
argument checker:
- If the handler accepts an O-type argument, unknown arguments
are passed down to it. It's up to O-type handlers to validate
their arguments
- Boolean types (eg. 'b' and '-') don't accept integers anymore,
only json-bool
- Argument types '/' and '.' are currently unsupported under QMP,
thus they're not handled
Signed-off-by: Luiz Capitulino <[email protected]>
|
4af9193ae954f87225e1ba5d527f6a13e37b1e0e
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4af9193ae954f87225e1ba5d527f6a13e37b1e0e
|
2010-07-01 14:27:13-03:00
|
pass info about hpets to seabios.]
Currently HPET ACPI table is created regardless of whether qemu actually
created hpet device. This may confuse some guests that don't check that
hpet is functional before using it. Solve this by passing info about
hpets in qemu to seabios via fw config interface. Additional benefit is
that seabios no longer uses hard coded hpet configuration. Proposed
interface supports up to 8 hpets. This is the number defined by hpet
spec.
Signed-off-by: Gleb Natapov <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
40ac17cd56eb5c5a89559ea0fa53f7eea80cbd07
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/40ac17cd56eb5c5a89559ea0fa53f7eea80cbd07
|
2010-06-14 11:12:53-05:00
|
arm_timer: fix oneshot mode
In oneshot mode, the delta needs to come from the TimerLoad register,
not the maximum limit.
Signed-off-by: Rabin Vincent <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
a9cf98d939c4f6539fad7e7d812ea16d96ba3dc9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a9cf98d939c4f6539fad7e7d812ea16d96ba3dc9
|
2010-05-21 12:00:22+02:00
|
ide: Avoid canceling IDE DMA
The reason for not actually canceling the I/O is because with
virtualization and lots of VM running, a guest fs may mistake a
overload of the host, as an IDE timeout. So rather than canceling the
I/O, it's safer to wait I/O completion and simulate that the I/O has
completed just before the io cancellation was requested by the
guest. This way if ntfs or an app writes data without checking for
-EIO retval, and it thinks the write has succeeded, it's less likely
to run into troubles. Similar issues for reads.
Furthermore because the DMA operation is splitted into many synchronous
aio_read/write if there's more than one entry in the SG table, without this
patch the DMA would be cancelled in the middle, something we've no idea if it
happens on real hardware too or not. Overall this seems a great risk for zero
gain.
This approach is sure safer than previous code given we can't pretend all guest
fs code out there to check for errors and reply the DMA if it was completed
partially, given a timeout would never materialize on a real harddisk unless
there are defective blocks (and defective blocks are practically only an issue
for reads never for writes in any recent hardware as writing to blocks is the
way to fix them) or the harddisk breaks as a whole.
Signed-off-by: Izik Eidus <[email protected]>
Signed-off-by: Andrea Arcangeli <[email protected]>
Signed-off-by: Kevin Wolf <[email protected]>
|
953844d102f5b682f0835f021f2ed2ad9fb7734c
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/953844d102f5b682f0835f021f2ed2ad9fb7734c
|
2010-08-03 15:57:22+02:00
|
qcow2: Avoid shadowing variable in alloc_clusters_noref()
The i loop iterator is shadowed by the next free cluster index. Both
using the variable name 'i' makes the code harder to read.
Signed-off-by: Stefan Hajnoczi <[email protected]>
Signed-off-by: Kevin Wolf <[email protected]>
|
508e0893686794be55cfaa336fea584b16a471d9
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/508e0893686794be55cfaa336fea584b16a471d9
|
2010-05-03 10:07:31+02:00
|
qdev: Revert the hack to let -net nic and pci_add set qdev ID
Setting the ID in pci_nic_init() is a blatant violation of the
DeviceState abstraction. Which even carries a comment advising
against this:
/* This structure should not be accessed directly. We declare it here
so that it can be embedded in individual device state structures. */
What's worse, it bypasses the code ensuring unique qdev IDs: "-device
virtio-net-pci,id=foo -net nic,id=foo -net nic,name=foo" happily
creates three qdevs with ID "foo". That's because qdev relies on
qemu_opts_create() to ensure unique IDs, but -net nic uses a different
QemuOptsList, which means id is in a different namespace. And its
name is not checked for uniqueness at all.
-net nic and pci_add are legacy. Use -device and device_add if you
want a NIC with a qdev ID.
This reverts what's still left of commit eb54b6dc "qdev: add id=
support for pci nics."
Signed-off-by: Markus Armbruster <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
1bb650420021ced718d550559034a5147c053068
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/1bb650420021ced718d550559034a5147c053068
|
2010-06-14 15:46:28-05:00
|
Monitor: Return before exiting with 'quit'
The 'quit' Monitor command (implemented by do_quit()) calls
exit() directly, this is problematic under QMP because QEMU
exits before having a chance to send the ok response.
Clients don't know if QEMU exited because of a problem or
because the 'quit' command has been executed.
This commit fixes that by moving the exit() call to the main
loop, so that do_quit() requests the system to quit, instead
of calling exit() directly.
Signed-off-by: Luiz Capitulino <[email protected]>
|
0e8d2b5575938b8876a3c4bb66ee13c5d306fb6d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/0e8d2b5575938b8876a3c4bb66ee13c5d306fb6d
|
2010-04-26 16:36:01-03:00
|
qcow2: More checks for qemu-img check
Implement some more refcount block related checks
Signed-off-by: Kevin Wolf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
746c3cb5d55a702ba6285e97d2a13671f09285d8
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/746c3cb5d55a702ba6285e97d2a13671f09285d8
|
2010-02-23 13:23:29-06:00
|
sh4: Fix compiler warning (fprintf format string)
When argument checking is enabled, gcc throws this error:
error: format not a string literal and no format arguments
The patch rewrites the statement to satisfy the compiler.
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
c8160fab31e7a27979196c338a305e7095dd8aea
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/c8160fab31e7a27979196c338a305e7095dd8aea
|
2010-04-14 01:04:02+02:00
|
cris: Prepare for CRISv10.
* Add prefix flag and special reg.
* Add interrupt lockout.
* Add CC_OP_MSTEP.
Signed-off-by: Edgar E. Iglesias <[email protected]>
|
fb9fb692312a84ebc6e9c10da6f374c5871ff7b0
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/fb9fb692312a84ebc6e9c10da6f374c5871ff7b0
|
2010-02-15 11:17:33+01:00
|
Monitor: Drop the print disabling mechanism
We can ignore calls to monitor_vprintf() in QMP mode and use
monitor_puts() directly in monitor_json_emitter().
This allows us to drop this ugly hack.
Signed-off-by: Luiz Capitulino <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
b8b08266bd58d26e9c6b529ab4130c13eaed3406
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/b8b08266bd58d26e9c6b529ab4130c13eaed3406
|
2010-02-19 15:18:18-06:00
|
block/curl: %Z is not a valid conversion specifier
Signed-off-by: malc <[email protected]>
|
48a402e693cbea9582472159931aa6799a6c80c7
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/48a402e693cbea9582472159931aa6799a6c80c7
|
2010-02-08 12:44:55+03:00
|
loop write in qemu_event_increment upon EINTR
Same as what qemu-kvm does.
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
652ce2d449f47cdc4d94eb67f2377504c06957ad
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/652ce2d449f47cdc4d94eb67f2377504c06957ad
|
2010-02-10 11:56:56-06:00
|
target-i386: Fix compiler warning
With argument checking for cpu_fprintf, gcc throws this warning:
CC i386-softmmu/helper.o
cc1: warnings being treated as errors
/qemu/ar7/target-i386/helper.c: In function ‘cpu_x86_dump_seg_cache’:
/qemu/ar7/target-i386/helper.c:220: error: format not a string literal and no format arguments
The code is correct, but current gcc versions don't detect this.
Therefore the patch rewrites the statement to satisfy the compiler.
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
e5c15efff67d0cda978d726a11e5996a88f29b6f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/e5c15efff67d0cda978d726a11e5996a88f29b6f
|
2010-04-08 21:42:26+02:00
|
Check availavility of -fstack-protector-all
Signed-off-by: Juan Quintela <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
a0f291fc101a7ab3e40850a329da2cc2f2cd1f2d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/a0f291fc101a7ab3e40850a329da2cc2f2cd1f2d
|
2010-01-26 14:59:20-06:00
|
Enable _FORTIFY_SOURCE=2
_FORTIFY_SOURCE is a Glibc feature which adds memory and string function
protection.
Signed-off-by: Kirill A. Shutemov <[email protected]>
Signed-off-by: Juan Quintela <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
849583050d5f6f782718be8cb50688978973fbea
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/849583050d5f6f782718be8cb50688978973fbea
|
2010-01-26 14:59:20-06:00
|
Allocate physical memory in low virtual address space
KVM on S390x requires the virtual address space of the guest's RAM to be
within the first 256GB.
The general direction I'd like to see KVM on S390 move is that this requirement
is losened, but for now that's what we're stuck with.
So let's just hack up qemu_ram_alloc until KVM behaves nicely :-).
Signed-off-by: Alexander Graf <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
6b02494d64a15476e26a6e8468623d01c4c75c58
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6b02494d64a15476e26a6e8468623d01c4c75c58
|
2009-12-05 17:36:02+01:00
|
posix-aio-compat: Fix error check
Checking for nbytes < 0 is pointless as long as it's a size_t. If we want to
use negative numbers for error codes, we should use signed types.
Signed-off-by: Kevin Wolf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
6769da29c7a3caa9de4020db87f495de692cf8e2
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/6769da29c7a3caa9de4020db87f495de692cf8e2
|
2009-12-03 15:26:00-06:00
|
Load global config files by default
A new option, -nodefconfig is introduced to prevent loading from the default
config location. Otherwise, two configuration files will be searched for,
qemu.conf and target-<TARGET_NAME>.conf.
To ensure that the default configuration is overridden by a user specified
config, we introduce a two stage option parsing mechanism.
Signed-off-by: Anthony Liguori <[email protected]>
|
292444cb87f3b883146ee30628a5922b1cde4073
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/292444cb87f3b883146ee30628a5922b1cde4073
|
2010-01-24 09:37:26-06:00
|
Introduce QList unit-tests
This suite contains tests to assure that QList API works as expected.
To execute it you should have check installed and build QEMU with
check support enabled (--enable-check-utests) and then run:
$ ./check-qlist
Patchworks-ID: 35333
Signed-off-by: Luiz Capitulino <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
3aa3dcfff66ca70d5983d3122f24724793046d66
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/3aa3dcfff66ca70d5983d3122f24724793046d66
|
2009-10-08 21:17:18-05:00
|
Check availability of uuid header / library
If available, the Universally Unique Identifier library
is used by the vdi block driver.
Other parts of QEMU (vl.c) could also use it.
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Aurelien Jarno <[email protected]>
|
ee682d27a5f1f43e21b22dd8c55716ba48d8af0d
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/ee682d27a5f1f43e21b22dd8c55716ba48d8af0d
|
2009-10-04 13:24:45+02:00
|
Fix conditional compilation (MIPS host)
Compilation for MIPS host (not part of official QEMU)
checks __mips_isa_rev which is not always defined.
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
aeec26d348363d6b03d3f2679d86d53017cf6dd4
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/aeec26d348363d6b03d3f2679d86d53017cf6dd4
|
2009-09-11 10:19:34-05:00
|
QMP: Output support
In the new Monitor output is always performed by only two
functions: do_info() and monitor_call_handler().
To support QMP output, we modify those functions to check if we
are in control mode. If so, we call monitor_protocol_emitter()
to emit QMP output, otherwise we do regular output.
QMP has two types of responses to issued commands: success and
error. The outputed data is always a JSON object.
Success responses have the following format:
{ "return": json-value, "id": json-value }
Error responses have the following format:
{ "error": { "class": json-string,
"desc": json-string,
"data": json-value } "id": json-value }
Please, note that the "id" key is part of the input code, and
thus is not added in this commit.
Signed-off-by: Luiz Capitulino <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
25b422eb4051b9b7473feea1ae848f1e3b4f799f
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/25b422eb4051b9b7473feea1ae848f1e3b4f799f
|
2009-12-03 09:41:23-06:00
|
eepro100: Remove unused device status entries
Once upon the time when QEMU hacking was fun
there was a brave knight who wanted to have
a driver for a special intel nic.
So he started by cloning ne2000.c which also
meant that the new born eepro100.c was
immediately three years old.
Other knights who also wanted to have fun and
take their part in the battle thought that it
would be a good idea to remove stupid code
which says "missing nic load, missing nic save".
They saved everything they saw, man and women,
ne2000 code and runtime address offsets, and
put all saved elements in a prison called
vm data.
When the first knight came back and noticed
the unhappy prisoners, he wanted to set them
free. But the keepers of the keys told him
that they would have to stay there forever
for compatibility reasons.
So our brave knight now takes a new effort
to save the souls of the poor prisoners by
removing their names.
Their bodies will have to rot in the dungeons
of compatibility forever, watched by the
keepers of the keys.
Patchworks-ID: 35635
Signed-off-by: Stefan Weil <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
3706c43f021918684cf19fe0f6ef8498815e4313
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/3706c43f021918684cf19fe0f6ef8498815e4313
|
2009-10-15 09:32:00-05:00
|
QEMU: MCE: Add MCE simulation to qemu/tcg
- MCE features are initialized when VCPU is intialized according to CPUID.
- A monitor command "mce" is added to inject a MCE.
- A new interrupt mask: CPU_INTERRUPT_MCE is added to inject the MCE.
aliguori: fix build for linux-user
Signed-off-by: Huang Ying <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
79c4f6b08009a1d23177c2be8bd003253cf3686a
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/79c4f6b08009a1d23177c2be8bd003253cf3686a
|
2009-07-09 16:04:53-05:00
|
Fix hxtool.
When converting from hx to texi format, hxtool (or to be
more precise sh which interprets hxtool) used standard
shell expansion of wildcards while writing lines to the
output.
Thus, something like "Password: ********"
looked very different in the generated documentation.
The patch disables this unwanted wildcard expansion.
Signed-off-by: Stefan Weil <[email protected]>
|
7d69c52ed8939b036fbd31488f9c7b4f5d7b8208
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/7d69c52ed8939b036fbd31488f9c7b4f5d7b8208
|
2009-07-02 17:54:34+00:00
|
Unbreak large mem support by removing kqemu
kqemu introduces a number of restrictions on the i386 target. The worst is that
it prevents large memory from working in the default build.
Furthermore, kqemu is fundamentally flawed in a number of ways. It relies on
the TSC as a time source which will not be reliable on a multiple processor
system in userspace. Since most modern processors are multicore, this severely
limits the utility of kqemu.
kvm is a viable alternative for people looking to accelerate qemu and has the
benefit of being supported by the upstream Linux kernel. If someone can
implement work arounds to remove the restrictions introduced by kqemu, I'm
happy to avoid and/or revert this patch.
N.B. kqemu will still function in the 0.11 series but this patch removes it from
the 0.12 series.
Paul, please Ack or Nack this patch.
Signed-off-by: Anthony Liguori <[email protected]>
|
4a1418e07bdcfaa3177739e04707ecaec75d89e1
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/4a1418e07bdcfaa3177739e04707ecaec75d89e1
|
2009-08-24 08:02:55-05:00
|
migrate.c: migrate_fd_put_buffer: Do not busyloop: stop writing if EWOULDBLOCK
The migration code is non-blocking, designed for live migration.
Practically migrate_fd_put_buffer busy-loops trying to write, as
on many machines EWOULDBLOCK==EAGAIN (look in include/asm-generic/errno.h).
Signed-off-by: Uri Lublin <[email protected]>
|
95b134ea02a3e2c2508f907db4ab1379ffdb0bef
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/95b134ea02a3e2c2508f907db4ab1379ffdb0bef
|
2009-05-20 09:12:57-05:00
|
qcow2: Order concurrent AIO requests on the same unallocated cluster
When two AIO requests write to the same cluster, and this cluster is
unallocated, currently both requests allocate a new cluster and the second one
merges the first one when it is completed. This means an cluster allocation, a
read and a cluster deallocation which cause some overhead. If we simply let the
second request wait until the first one is done, we improve overall performance
with AIO requests (specifially, qcow2/virtio combinations).
This patch maintains a list of in-flight requests that have allocated new
clusters. A second request touching the same cluster is limited so that it
either doesn't touch the allocation of the first request (so it can have a
non-overlapping allocation) or it waits for the first request to complete.
Signed-off-by: Kevin Wolf <[email protected]>
Signed-off-by: Anthony Liguori <[email protected]>
|
f214978a427ea40b0b86af10548fe0270f6d0db0
|
qemu
|
devign
| 0 |
https://github.com/qemu/qemu
|
https://github.com/qemu/qemu/commit/f214978a427ea40b0b86af10548fe0270f6d0db0
|
2009-09-09 17:31:26-05:00
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.