On 01/31/2012 09:49 PM, Anthony Liguori wrote:
+DEFINE_PROP_HEX32("iobase", PCSpkState, iobase, -1),
+DEFINE_PROP_PTR("pit", PCSpkState, pit),
Please don't introduce a pointer property here. They cannot be used in
a meaningful way in qdev. Why not register a link in
instance
On Wed, Feb 01, 2012 at 06:44:42PM +1300, Alexey Korolev wrote:
> On 31/01/12 22:43, Avi Kivity wrote:
> > On 01/31/2012 11:40 AM, Avi Kivity wrote:
> >> On 01/27/2012 06:42 AM, Alexey Korolev wrote:
> >>> On 27/01/12 04:12, Avi Kivity wrote:
> On 01/26/2012 04:36 PM, Michael S. Tsirkin wrote:
On 31/01/12 22:43, Avi Kivity wrote:
> On 01/31/2012 11:40 AM, Avi Kivity wrote:
>> On 01/27/2012 06:42 AM, Alexey Korolev wrote:
>>> On 27/01/12 04:12, Avi Kivity wrote:
On 01/26/2012 04:36 PM, Michael S. Tsirkin wrote:
> On Thu, Jan 26, 2012 at 03:52:27PM +0200, Avi Kivity wrote:
>>
In order to safely drive a device with a userspace driver, or to pass
it through to a guest system, we must first make sure that the device
is isolated in such a way that it cannot interfere with other devices
on the system. This isolation is only available on some systems and
will generally requi
This patch adds code to the code for the powernv platform to create
and populate isolation groups on hardware using the p5ioc2 PCI host
bridge used on some IBM POWER systems.
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: David Gibson
---
arch/powerpc/platforms/powernv/pci-p5ioc2.c | 14 +
This patch series introduces a new infrastructure to the driver core
for representing "device isolation groups". That is, groups of
devices which can be "isolated" in such a way that the rest of the
system can be protected from them, even in the presence of userspace
or a guest OS directly driving
This patch adds code to the code for the powernv platform to create
and populate isolation groups on hardware using the p7ioc (aka IODA) PCI host
bridge used on some IBM POWER systems.
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: David Gibson
---
arch/powerpc/platforms/powernv/pci-ioda.c
raw-posix driver changes for bdrv_reopen_xx functions to
safely reopen image files. Reopening of image files while
changing hostcache dynamically is handled here.
Signed-off-by: Supriya Kannery
Index: qemu/block/raw.c
===
--- qemu.
vmdk driver changes for bdrv_reopen_xx functions to
safely reopen image files. Reopening of image files while
changing hostcache flag dynamically is handled here.
Signed-off-by: Supriya Kannery
Index: qemu/block/vmdk.c
===
--- qemu.
win32 driver changes for bdrv_reopen_xx functions to
safely reopen image files. Reopening of image files while
changing hostcache dynamically is handled here.
Signed-off-by: Supriya Kannery
Index: qemu/block/raw-win32.c
===
--- qem
Struct BDRVReopenState along with three reopen related functions
introduced for handling reopening of images safely. This can be
extended by each of the block drivers to reopen respective
image files.
Signed-off-by: Supriya Kannery
Index: qemu/block.c
New command "block_set_hostcache" added for dynamically changing
host pagecache setting of a block device.
Usage:
block_set_hostcache
= block device
= on/off
Example:
(qemu) block_set_hostcache ide0-hd0 off
Signed-off-by: Supriya Kannery
---
block.c | 54 +
Enhance "info block" to display hostcache setting for each
block device.
Example:
(qemu) info block
ide0-hd0: removable=0 file=../rhel6-32.raw ro=0 drv=raw encrypted=0
Enhanced to display "hostcache" setting:
(qemu) info block
ide0-hd0: removable=0 hostcache=1 file=../rhel6-32.raw ro=0 drv=raw en
New error classes defined for file reopen failure and data
sync error
Signed-off-by: Supriya Kannery
---
qerror.c |8
qerror.h |6 ++
2 files changed, 14 insertions(+)
Index: qemu/qerror.c
===
--- qemu.orig/qe
For changing host pagecache setting of a running VM, it is
important to have a safe way of reopening its image file.
Following patchset introduces:
* a generic way to reopen image files safely.
In this approach, before reopening an image, for each
block driver, its state will be
On Wed, Feb 1, 2012 at 12:37 PM, Anthony Liguori wrote:
> On 01/31/2012 07:44 PM, Alexander Graf wrote:
>>
>>
>> On 01.02.2012, at 02:35, Paul Brook wrote:
>>
We could also just change machine->init() and pass the dtb in there. In
a
QOM world these would become machine device proper
On 01/31/2012 07:44 PM, Alexander Graf wrote:
On 01.02.2012, at 02:35, Paul Brook wrote:
We could also just change machine->init() and pass the dtb in there. In a
QOM world these would become machine device properties anyways.
machine->init(ram_size, boot_devices,
kernel
On 01/31/2012 07:35 PM, Paul Brook wrote:
We could also just change machine->init() and pass the dtb in there. In a
QOM world these would become machine device properties anyways.
machine->init(ram_size, boot_devices,
kernel_filename, kernel_cmdline, initrd_filename,
cpu_
On Mon, Jan 30, 2012 at 12:48 PM, Anthony Liguori wrote:
>
> On Jan 29, 2012 8:41 PM, "John Williams"
> wrote:
>>
>> There's an opportunity here - QEMU needs the cmdline ability to load
>> random binaries/elfs anyway, such as
>>
>> --load file@address
>> >>>
>> >>>
>> >>>
>> >
On 01.02.2012, at 02:35, Paul Brook wrote:
>> We could also just change machine->init() and pass the dtb in there. In a
>> QOM world these would become machine device properties anyways.
>>
>>machine->init(ram_size, boot_devices,
>> kernel_filename, kernel_cmdline, initrd_fi
> We could also just change machine->init() and pass the dtb in there. In a
> QOM world these would become machine device properties anyways.
>
> machine->init(ram_size, boot_devices,
> kernel_filename, kernel_cmdline, initrd_filename,
> cpu_model);
>
> Essentially we should
On Tue, Jan 31, 2012 at 12:00:30PM +0200, Dmitry Zamaruev wrote:
>This is used in many places.
>Maybe to simulate 'private' variables and access methods like in C++.
>
>If you define structure in .c file then every function that works with
>this structure must reside in same file. And any other cod
Kevin Wolf writes:
> Am 23.01.2012 13:49, schrieb Göran Weinholt:
>> There are two special cases in the address fields of the multiboot
>> format. If mh_load_end_addr is zero then the whole image file should
>> be loaded and if mh_bss_end_addr is zero then there is no bss segment.
>> With this ch
On 01.02.2012, at 01:11, Grant Likely wrote:
> If compiled with CONFIG_FDT, allow user to specify a device tree file using
> the -dtb argument. If the machine supports it then the dtb will be loaded
> into memory and passed to the kernel on boot.
>
> v2: - Enable for all arm platforms by making
If compiled with CONFIG_FDT, allow user to specify a device tree file using
the -dtb argument. If the machine supports it then the dtb will be loaded
into memory and passed to the kernel on boot.
v2: - Enable for all arm platforms by making arm_boot use the filename directly
- Fix style issue
The compat LOOP_SET_STATUS ioctl uses struct old_dev_t in its passed
struct. That variable type is vastly different between different
architectures. Implement wrapping around it so we can use it.
This fixes running arm kpartx on an x86_64 host for me.
Signed-off-by: Alexander Graf
---
I messed
This patch implements all ioctls currently implemented by device mapper,
enabling us to run dmsetup and kpartx inside of linux-user.
Signed-off-by: Alexander Graf
---
linux-user/ioctls.h| 33 +++
linux-user/syscall.c | 226
linux-
Some BLK ioctls passed sizeof(x) into a macro that already did sizeof() on
the passed in argument, rendering the size information inside the ioctl be
the size of the host default integer type.
Signed-off-by: Alexander Graf
---
linux-user/syscall_defs.h |8 +---
1 files changed, 5 inserti
The compat LOOP_SET_STATUS ioctl uses struct old_dev_t in its passed
struct. That variable type is vastly different between different
architectures. Implement wrapping around it so we can use it.
This fixes running arm kpartx on an x86_64 host for me.
Signed-off-by: Alexander Graf
---
linux-use
On 01/31/2012 04:48 PM, Jan Kiszka wrote:
On 2012-01-31 23:40, Anthony Liguori wrote:
Why is what's in the tree not usable?
Just don't do pcspk_init as a static inline (which is not that nice to
do anyway) and you don't need to worry about the availability of an
accessor.
The current pattern
This patch adds an ioctl definition for BLKSSZGET.
Signed-off-by: Alexander Graf
---
linux-user/ioctls.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/linux-user/ioctls.h b/linux-user/ioctls.h
index a9d333a..7245ff0 100644
--- a/linux-user/ioctls.h
+++ b/linux-user/ioc
As part of our OBS build process, we also want to be able to create kiwi images
for ARM on x86 hardware. One of the crucial bits there is the kpartx tool, since
that allows us to map images on the fly through device mapper.
So this patch set goes in and implements all the device mapper ioctls and
Am 01.02.2012 00:04, schrieb Charles Arnold:
> The Virtual Hard Disk Image Format Specification allows for three
> types of hard disk formats, Fixed, Dynamic, and Differencing. Qemu
> currently only supports Dynamic disks. This patch adds support for
> the Fixed Disk format.
>
> Usage:
> Ex
Riku,
Am 31.01.2012 10:29, schrieb riku.voi...@linaro.org:
> From: Riku Voipio
>
> The collection of simpler linux-user patches submitted since release of 1.0.
> To be sent as pull request later this week unless bugs found.
What about this one?
http://patchwork.ozlabs.org/patch/117176/
It mig
Thanks Andreas,
The 'TODO uuid is missing' comment in the patch is from the
original sources (as well as many '//' comments). The vhd footer
and header data structures contain a field for a UUID but no code
was ever developed to generate one.
The revised patch is below after running scripts/ch
On 2012-01-31 23:40, Anthony Liguori wrote:
> On 01/31/2012 04:00 PM, Jan Kiszka wrote:
>> On 2012-01-31 21:49, Anthony Liguori wrote:
>>> On 01/31/2012 11:41 AM, Jan Kiszka wrote:
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at t
On 01/31/2012 04:00 PM, Jan Kiszka wrote:
On 2012-01-31 21:49, Anthony Liguori wrote:
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszka
Heh, I did this to
On 2012-01-31 23:38, Anthony Liguori wrote:
> On 01/31/2012 04:05 PM, Jan Kiszka wrote:
>> On 2012-01-31 22:02, Anthony Liguori wrote:
>>> On 01/31/2012 11:41 AM, Jan Kiszka wrote:
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output l
On 01/31/2012 04:05 PM, Jan Kiszka wrote:
On 2012-01-31 22:02, Anthony Liguori wrote:
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. T
Le mardi 31 janvier 2012 à 22:01 +0200, Riku Voipio a écrit :
> On Sun, Jan 22, 2012 at 01:27:13PM +0100, Laurent Vivier wrote:
> > This serie of patches has already been sent, more or less, several time,
> > last time in july 2011.
>
> > For chrooted environment, it allows to define the default
Hi,
Markus Armbruster a écrit :
Are single sided floppies broken before the patch? How?
Yes. For head > 0, wrong sector number is calculated, so data is
read/written at wrong place on underlying block device.
Fortunately, mostly nobody is still using single-sided floppies (only
some 360 kB flo
Greetings from
MarkPlus Institute of Marketing Malaysia.
We would like
to inform you that MarkPlus Institute of Marketing
(MIM) will be holding two training programs on
February 2012.
·
One-day
program : EFFECTIVE NEGOTIATION
SKILL on 14 February 2012
·
Two-day
program : PROFES
Hi,
Markus Armbruster a écrit :
Looks sane, except for the migration of media rate. See my reply to
7/9.
I'm not very fluent with requirements for store/save/migration
compatibility things, so can someone knowing them can look at the
migration of media rate problem? Paolo?
Markus reply i
Markus Armbruster a écrit :
Hervé Poussineau writes:
Markus Armbruster a écrit :
Hervé Poussineau writes:
DIR and CCR registers share the same address ; DIR is read-only
while CCR is write-only
Looks like guest writes to CCR are silently ignored before this patch.
Is that correct?
Yes.
Hello Charles,
Am 31.01.2012 20:03, schrieb Charles Arnold:
> The Virtual Hard Disk Image Format Specification allows for three
> types of hard disk formats, Fixed, Dynamic, and Differencing. Qemu
> currently only supports Dynamic disks. This patch adds support for
> the Fixed Disk format.
>
>
On 2012-01-31 22:02, Anthony Liguori wrote:
> On 01/31/2012 11:41 AM, Jan Kiszka wrote:
>> In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
>> 8 but keeps track of the RTC output level and applies it when legacy
>> mode is turned off again. This value has to be preserved acros
On 2012-01-31 21:49, Anthony Liguori wrote:
> On 01/31/2012 11:41 AM, Jan Kiszka wrote:
>> Convert the PC speaker device to a qdev ISA model. Move the public
>> interface to a dedicated header file at this chance.
>>
>> Signed-off-by: Jan Kiszka
>
> Heh, I did this too more or less the same way.
On 01/31/2012 03:49 PM, Jan Kiszka wrote:
On 2012-01-31 22:40, Anthony Liguori wrote:
On 01/31/2012 12:46 PM, Jan Kiszka wrote:
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM
On 2012-01-31 22:40, Anthony Liguori wrote:
> On 01/31/2012 12:46 PM, Jan Kiszka wrote:
>> Applying the concept used for the *PICs once again: establish a base
>> class for the i8254 that can be used both by the current user space
>> emulation and the upcoming KVM in-kernel version. We share most o
On 01/31/2012 12:46 PM, Jan Kiszka wrote:
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM in-kernel version. We share most of the
public interface of the i8254, specifically to
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. This value has to be preserved across save/
restore as it cannot be reconstructed otherwi
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszka
Heh, I did this too more or less the same way. Some comments below:
---
arch_init.c|1 +
hw/
This fixes a bug when using -m isa-serial where qemu-ga will
hang on a read()'s when communicating to the host via isa-serial.
Original fix by Michael Roth.
Signed-off-by: Luiz Capitulino
---
qemu-ga.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/qemu-ga.c b/qemu-ga
On Sun, Jan 22, 2012 at 01:27:13PM +0100, Laurent Vivier wrote:
> This serie of patches has already been sent, more or less, several time,
> last time in july 2011.
> For chrooted environment, it allows to define the default cpu model as we
> can't use '-cpu' argument.
We now can, with QEMU_CPU
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use t
Jan Kiszka wrote:
There are scenarios on Linux with some SDL versions where
handle_activation is continuous invoked with state = SDL_APPINPUTFOCUS
and gain = 0 while we grabbed the input. This causes a ping-pong when we
grab the input after an absolute mouse entered the window.
As this sdl_grab_
Signed-off-by: Luiz Capitulino
---
qapi-schema-guest.json | 23 +++
qga/guest-agent-commands.c | 10 ++
2 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/qapi-schema-guest.json b/qapi-schema-guest.json
index cc914ad..9b9ecc9 100644
--- a/qapi-sche
Signed-off-by: Luiz Capitulino
---
qapi-schema-guest.json | 28
qga/guest-agent-commands.c | 10 ++
2 files changed, 38 insertions(+), 0 deletions(-)
diff --git a/qapi-schema-guest.json b/qapi-schema-guest.json
index da2b240..cc914ad 100644
--- a/qapi
v8
o Split the guest-suspend command into guest-suspend-disk, guest-suspend-ram
and guest-suspend-hybrid (this required some refactorings)
o Drop ga_has_support_level usage
qapi-schema-guest.json | 75
qemu-ga.c | 20 -
qga/guest-agent-commands.c |
From: Sergei Trofimovich
Current './configure --static && make' fails for me:
LINK qemu-nbd
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lssl3
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot fin
Hi everyone,
I'm trying to build qemu on Oracle Solars 11 x64. I've figure out that I
need to set the --disable-guest-agent for ./configure, but there are
other errors I do not know how to fix.
Setting LD_LIBRARY_PATH to /usr/lib/mps/amd64 helps but at least one
error still remains:
ld: fa
Hi everyone,
I'm trying to build qemu on Oracle Solars 11 x64. I've figure out that I
need to set the --disable-guest-agent for ./configure, but there are
other errors I do not know how to fix.
Setting LD_LIBRARY_PATH to /usr/lib/mps/amd64 helps but at least one
error still remains:
ld: fa
From: Sergei Trofimovich
Added wrapper around pkg-config to allow:
- safe options injection via ${QEMU_PKG_CONFIG_FLAGS}
- spaces in path to pkg-config
Signed-off-by: Sergei Trofimovich
CC: Peter Maydell
---
configure | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff
The Virtual Hard Disk Image Format Specification allows for three
types of hard disk formats, Fixed, Dynamic, and Differencing. Qemu
currently only supports Dynamic disks. This patch adds support for
the Fixed Disk format.
Usage:
Example 1: qemu-img create -f vpc -o type=fixed [size]
E
Same as for the APIC: To enable migration between accelerated and
non-accelerated models, we need to arm the channel 0 timer only inside
the emulated PIT model. The common code just saves/restores that timer
to the the next_transition_time field.
Signed-off-by: Jan Kiszka
---
hw/i8254.c|
This provides the required user space stubs to enable the in-kernel
i8254 emulation of KVM.
The in-kernel model supports lost tick compensation according to the
"delay" policy. This is enabled by default and can be switched off via a
device property.
Depending on the feature set of the host kerne
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM in-kernel version. We share most of the
public interface of the i8254, specifically to the pcspk, vmstate, reset
and certain init p
To be used for in-kernel PIT emulation.
Signed-off-by: Jan Kiszka
---
kvm-all.c | 10 ++
kvm-stub.c |5 +
kvm.h |1 +
3 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index 3f2460f..8df5235 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@
This adds another piece of qemu-kvm to upstream: The accelerated
in-kernel model of the i8254. It does this in the same fashion as the
interrupt controllers were already introduced. And it even has one bug
less than qemu-kvm: PC speaker output still works with KVM acceleration
enabled.
The patches
Am 31.01.2012 15:48, schrieb Kevin Wolf:
Am 31.01.2012 15:40, schrieb Peter Maydell:
On 31 January 2012 13:35, Kevin Wolf wrote:
Am 27.01.2012 18:53, schrieb Stefan Weil:
+Hosts:
+--
+
+LINUX
+L: qemu-devel@nongnu.org
+S: Maintained
+F: linux-*
+F: linux-headers/
+
+POSIX
+L: qemu-devel@n
To both avoid that kvm_irqchip_in_kernel always has to be paired with
kvm_enabled and that the former ends up in a function call, implement it
like the latter. This means keeping the state in a global variable and
defining kvm_irqchip_in_kernel as a preprocessor macro.
Signed-off-by: Jan Kiszka
-
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. This value has to be preserved across save/
restore as it cannot be reconstructed otherwise.
Signed-off-by: Jan Kiszka
---
hw/hpet
Move the public interface of the PIT into its own header file and update
all users.
Signed-off-by: Jan Kiszka
---
hw/alpha_dp264.c |1 +
hw/hpet.c |1 +
hw/i82378.c|1 +
hw/i8254.c |1 +
hw/i8254.h | 54
HPET legacy emulation will require control over the PIT IRQ output. To
enable this, add support for an alternative IRQ output object to the PIT
factory function. If the isa_irq number is < 0, this object will be
used.
This also removes the IRQ number property from the PIT class as we now
use a gen
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszka
---
arch_init.c|1 +
hw/i82378.c|3 +-
hw/mips_jazz.c |3 +-
hw/pc.c|3 +-
hw/pc.h|4 ---
hw/pcspk.c |
Instead of providing 4 individual query functions for mode, gate, output
and initial counter state, introduce a service that queries all
information at once. This comes with tiny additional costs for
pcspk_callback but with a much cleaner interface. Also, it will simplify
the implementation of the
When the HPET enters legacy mode, the IRQ output of the PIT is
suppressed and replaced by the HPET timer 0. But the current code to
emulate this was broken in many ways. It reset the PIT state after
re-enabling, it worked against a stale static PIT structure, and it did
not properly saved/restored
This is a preparatory series to allow the introduction of the KVM
in-kernel PIT. It also fixes various bugs in the PIT and HPET code,
see patches for details.
Changes in V3:
- rebased over master
- tuned pic_init interface to avoid isa_get_irq(NULL, ...)
Jan Kiszka (7):
i8254: Do not raise IR
Avoid changing the IRQ level to high on reset as it may trigger spurious
events. Instead, open-code the effects of pit_load_count(0) in the reset
handler.
Signed-off-by: Jan Kiszka
---
hw/i8254.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/hw/i8254.c b/hw/i825
On Sun, Jan 29, 2012 at 17:02, 马磊 wrote:
> Hi,
> qemu-img is only to support create/info and so on whithout writting
> operation to the image file.
> I have ported the reading operation for a image file form grub2 to
> qemu-img. But NTFS document online is not detailed enough, how to do
If the host's page size is equal to or smaller than the target's, native
execve() will fail appropriately with E2BIG if called with too big an
environment for the target to handle. It may falsely succeed, however, if
the host's page size is bigger, and feed the executed target process an
environmen
On 01/31/2012 05:47 PM, Anthony Liguori wrote:
static void object_initialize(Object *obj)
{
PIIX3State *s = PIIX3(obj);
ChildProperty props[] = {
{ "pic[0]", TYPE_I8259, &s->pic[0] },
{ "pic[1]", TYPE_I8259, &s->pic[1] },
};
object_property_add_children(obj,
On 2012-01-31 17:49, Anthony Liguori wrote:
> On 01/31/2012 10:42 AM, Jan Kiszka wrote:
>> On 2012-01-31 15:56, Anthony Liguori wrote:
>>> On 01/31/2012 08:51 AM, Jan Kiszka wrote:
On 2012-01-31 15:47, Anthony Liguori wrote:
> On 01/31/2012 08:34 AM, Jan Kiszka wrote:
>> On 2012-01-26
On 01/31/2012 10:42 AM, Jan Kiszka wrote:
On 2012-01-31 15:56, Anthony Liguori wrote:
On 01/31/2012 08:51 AM, Jan Kiszka wrote:
On 2012-01-31 15:47, Anthony Liguori wrote:
On 01/31/2012 08:34 AM, Jan Kiszka wrote:
On 2012-01-26 20:00, Anthony Liguori wrote:
@@ -548,6 +550,13 @@ static int pi
On 01/31/2012 10:19 AM, Jan Kiszka wrote:
On 2012-01-31 17:12, Anthony Liguori wrote:
On 01/31/2012 08:58 AM, Paolo Bonzini wrote:
On 01/31/2012 03:51 PM, Jan Kiszka wrote:
BTW, this is yet another benefit of making structures public. You can take the
address of a child and set link fields di
On 2012-01-31 15:56, Anthony Liguori wrote:
> On 01/31/2012 08:51 AM, Jan Kiszka wrote:
>> On 2012-01-31 15:47, Anthony Liguori wrote:
>>> On 01/31/2012 08:34 AM, Jan Kiszka wrote:
On 2012-01-26 20:00, Anthony Liguori wrote:
> @@ -548,6 +550,13 @@ static int piix3_realize(PCIDevice *dev)
>
Am 31.01.2012 14:59, schrieb Anthony Liguori:
> On 01/30/2012 05:41 PM, Andreas Färber wrote:
>> Am 30.01.2012 19:55, schrieb Juan Quintela:
>>> Please send in any agenda items you are interested in covering.
>>
>> QOM roadmap update:
>> * Series 3/4 is on the list.
>> -> Please officially designa
On 2012-01-31 17:12, Anthony Liguori wrote:
> On 01/31/2012 08:58 AM, Paolo Bonzini wrote:
>> On 01/31/2012 03:51 PM, Jan Kiszka wrote:
>
> BTW, this is yet another benefit of making structures public. You can
> take the
> address of a child and set link fields directly without acc
PIT and PCSPK are emulated by the hypervisor so we don't need to emulate
them in Qemu: this patch prevents Qemu from waking up needlessly at
PIT_FREQ on Xen.
Signed-off-by: Stefano Stabellini
---
hw/pc.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/hw/pc.c b/h
Use the newly introduced HVM_PARAM_BUFIOREQ_EVTCHN to receive
notifications for buffered io events.
After the first notification is received leave the event channel masked
and setup a timer to process the rest of the batch.
Once we have completed processing the batch, unmask the event channel
and d
On 01/31/2012 08:58 AM, Paolo Bonzini wrote:
On 01/31/2012 03:51 PM, Jan Kiszka wrote:
>
> BTW, this is yet another benefit of making structures public. You can take the
> address of a child and set link fields directly without accessors.
Well, that has two sides. We introduced properties to av
There is no reason why the minimum timeout should be 1sec, it could
easily be 1h and we would save lots of cpu cycles.
Signed-off-by: Stefano Stabellini
---
qemu-timer.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index de20852..84b970e 1
Also delta in qemu_next_alarm_deadline is a 64 bit value so set the
default to INT64_MAX instead of INT32_MAX.
Signed-off-by: Stefano Stabellini
---
qemu-timer.c | 10 --
1 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index 29410f1..de20852 1
rtc_clock is only used by the RTC emulator (mc146818rtc.c), however Xen
has its own RTC emulator in the hypervisor so we can disable it.
Signed-off-by: Stefano Stabellini
---
xen-all.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/xen-all.c b/xen-all.c
index fd39168
Fix win32_rearm_timer and mm_rearm_timer: they should be able to handle
INT64_MAX as a delta parameter without overflowing.
Also, the next deadline in ms should be calculated rounding down rather
than up (see unix_rearm_timer and dynticks_rearm_timer).
Finally ChangeTimerQueueTimer takes an unsign
Hi all,
this small patch series prevents QEMU from waking up needlessly on Xen
several times a second in order to check some timers.
The first patch stops QEMU from emulating the PIT on Xen, the second
patch disables the rtc_clock entirely.
The third patch makes use of a new mechanism to receiv
On 2012-01-31 15:58, Paolo Bonzini wrote:
> On 01/31/2012 03:51 PM, Jan Kiszka wrote:
BTW, this is yet another benefit of making structures public. You can
take the
address of a child and set link fields directly without accessors.
>> Well, that has two sides. We introduced
On 2012-01-31 15:26, Jan Kiszka wrote:
> Also note that the HPET is not a part of the PIIX, so composition is
> wrong here. The RTC is again.
Err, forgot my nonsense. The HPET is part of the PIIX. Dunno, I was
somehow thinking of the IOAPIC while reading "HPET". Too few sleep, I
guess...
Jan
--
On Wed, 25 Jan 2012, Stefano Stabellini wrote:
> Hi all,
> this is the fourth version of the Xen save/restore patch series.
> We have been discussing this issue for quite a while on #qemu and
> qemu-devel:
>
>
> http://marc.info/?l=qemu-devel&m=132346828427314&w=2
> http://marc.info/?l=qemu-devel
On 01/31/2012 03:12 PM, Anthony Liguori wrote:
Don't use VMState. Just open code a save/restore function. VMState is
too limited in how it handles complex data structures.
I really believe the only long term solution we're going to get to here
is something that uses a builder interface (like
1 - 100 of 192 matches
Mail list logo
