On 04.01.2013, at 00:07, Scott Wood wrote:
> On 01/03/2013 12:31:47 PM, Alexander Graf wrote:
>> On 22.12.2012, at 03:15, Scott Wood wrote:
>> > Critical interrupts on FSL MPIC are not supposed to pay
>> > attention to priority, IACK, EOI, etc. On the currently modeled
>> > version it's not supp
Get rid of get_system_io() usage.
Signed-off-by: Gerd Hoffmann
---
hw/acpi_piix4.c | 20 +---
1 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
index f53b969..06a8aca 100644
--- a/hw/acpi_piix4.c
+++ b/hw/acpi_piix4.c
@@ -57,6 +57
On 04.01.2013, at 00:25, Scott Wood wrote:
> Respin of the patches from the 12/21 patchset that were not already applied.
Thanks, applied all to ppc-next.
Alex
>
> Scott Wood (4):
> openpic: fix sense and priority bits
> openpic: IRQ_check: search the queue a word at a time
> openpic: move
Hi,
This patch series improves the debug devices we have. isa-debugcon is
switched over to the memory api. isa-debug-exit is added and replaces
the hard-coded bochs debug port. pc-testdev (used by kvm-unit-tests) is
added.
please pull,
Gerd
The following changes since commit 25bbf61e4bacd
Signed-off-by: Gerd Hoffmann
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 9538041..1e9fd86 100755
--- a/configure
+++ b/configure
@@ -4240,6 +4240,7 @@ FILES="$FILES pc-bios/spapr-rtas/Makefile"
FILES="$FILES roms/seabios/Make
Signed-off-by: Gerd Hoffmann
---
hw/pc.c | 23 +++
hw/pc.h |1 +
hw/pc_piix.c |1 +
hw/pc_q35.c |1 +
4 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 71902e2..5ec3bd5 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -886,6
The Buildbot has detected a new failure on builder s390-next_x86_64_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_x86_64_debian_6_0/builds/503
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuz
Hi,
This patch series carries a bunch of acpi bits: Some small incremental
fixes for the memory api conversion and dsdt autoloading. The later
makes q35 JustWork[tm] without explicit -acpitable switch.
please pull,
Gerd
The following changes since commit 25bbf61e4bacd1e4fa4115ffcf151051b9d
The Buildbot has detected a new failure on builder s390-next_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_i386_debian_6_0/builds/504
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Signed-off-by: Gerd Hoffmann
---
hw/debugexit.c| 75 +++
On 04.01.2013, at 05:22, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
>> Sent: Friday, January 04, 2013 7:08 AM
>> To: Alexander Graf
>> Cc: jjhe...@linux.vnet.ibm.com; Christian Borntraeger; Anthony Liguori; qemu-
>> de...
Also some QOM glue while being at it.
Signed-off-by: Gerd Hoffmann
---
hw/debugcon.c | 31 ---
1 files changed, 24 insertions(+), 7 deletions(-)
diff --git a/hw/debugcon.c b/hw/debugcon.c
index 14f83f1..e8a855e 100644
--- a/hw/debugcon.c
+++ b/hw/debugcon.c
@@ -29,
From: Lucas Meneghel Rodrigues
Add a test device which supports the kvmctl ioports,
so one can run the KVM unittest suite.
Intended Usage:
qemu-system-x86_64 -nographic \
-device pc-testdev \
-device isa-debug-exit,iobase=0xf4,iosize=0x04 \
-kernel /path/to/kvm/unittests/msr.flat
W
Get rid of get_system_io() usage.
Signed-off-by: Gerd Hoffmann
---
hw/acpi_ich9.c |6 --
hw/acpi_ich9.h |4 +++-
hw/lpc_ich9.c |2 +-
3 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/hw/acpi_ich9.c b/hw/acpi_ich9.c
index 37a50e6..d2f9808 100644
--- a/hw/acpi_ich9.c
Prehistoric leftover, zap it. We poweroff via acpi these days.
And having a port (0x501,0x502) where any random guest write will make
qemu exit -- with no way to turn it off -- is a bad joke anyway.
Signed-off-by: Gerd Hoffmann
---
hw/pc.c | 41 -
1 fi
On 04.01.2013, at 09:57, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, January 04, 2013 2:11 PM
>> To: Bhushan Bharat-R65777
>> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
>> Anthony
>>
On 03.01.2013, at 23:37, Stuart Yoder wrote:
> From: Stuart Yoder
>
> Signed-off-by: Stuart Yoder
Thanks, adjusted the patch slightly (fix to apply, add patch description) and
applied it to ppc-next.
Alex
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, January 04, 2013 2:11 PM
> To: Bhushan Bharat-R65777
> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
> Anthony
> Liguori; qemu-devel@nongnu.org qemu-devel
> Subject: Re: [Qemu-dev
Store --extra-cflags and --extra-ldflags in config-host.mak,
then pass them on to the pixman configure script.
Cc: Scott Wood
Signed-off-by: Gerd Hoffmann
---
Makefile |2 +-
configure |4
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index a7a
Signed-off-by: Gerd Hoffmann
---
tests/rtc-test.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/tests/rtc-test.c b/tests/rtc-test.c
index 02edbf5..548200a 100644
--- a/tests/rtc-test.c
+++ b/tests/rtc-test.c
@@ -201,6 +201,10 @@ static void set_year_20xx(void)
g
On Thu, Jan 03, 2013 at 01:51:02PM -0600, Troy Benjegerdes wrote:
> On Thu, Jan 03, 2013 at 01:39:48PM +0100, Stefan Hajnoczi wrote:
> > On Wed, Jan 02, 2013 at 12:26:37PM -0600, Troy Benjegerdes wrote:
> > > The probability may be 'low' but it is not zero. Just because it's
> > > hard to calculate
On Thu, Jan 03, 2013 at 01:53:20PM -0500, Christoffer Dall wrote:
> On Thu, Jan 3, 2013 at 6:50 AM, Andreas Färber wrote:
> >
> >> The culprit seems to be when the process runs out of virtual address
> >> space on 32-bit systems due to some subsystem (virtio?) creating a
> >> large number of pthre
Hi,
I'm seeing the following segfault of qemu-system-i386 and
qemu-system-x86_64 with master. git bisect points to
258711c6448c44b60b0fecef1d3b09c71e23e304.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xea930b70 (LWP 14297)]
0x in ?? ()
(gdb) bt
#0 0x000
Am 04.01.2013 10:43, schrieb Gerd Hoffmann:
> Signed-off-by: Gerd Hoffmann
> ---
> tests/rtc-test.c |4
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/tests/rtc-test.c b/tests/rtc-test.c
> index 02edbf5..548200a 100644
> --- a/tests/rtc-test.c
> +++ b/tests/rtc-test
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, January 04, 2013 2:11 PM
> To: Bhushan Bharat-R65777
> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
> Anthony
> Liguori; qemu-devel@nongnu.org qemu-devel
> Subject: Re: [Qemu-dev
We already used to support the external proxy facility of FSL MPICs,
but only implemented it halfway correctly.
This patch adds support for
* dynamic enablement of the EPR facility
* interrupt acknowledgement only when the interrupt is delivered
This way the implementation now is closer to r
Hi,
i have observed the following with qemu-kvm-1.2.0 which I think is not right:
a) if the CDROM is locked and I sent a eject command I get the error that the
CDROM is locked, but its ejected nevertheless.
b) if I eject the CDROM in the OS I see tray-open=1 and locked=1. In the
tray-open=1 stat
Am 04.01.2013 09:16, schrieb Gerd Hoffmann:
> Hi,
>
> This patch series improves the debug devices we have. isa-debugcon is
> switched over to the memory api. isa-debug-exit is added and replaces
> the hard-coded bochs debug port. pc-testdev (used by kvm-unit-tests) is
> added.
Missing some
On 04.01.2013, at 11:23, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, January 04, 2013 2:11 PM
>> To: Bhushan Bharat-R65777
>> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
>> Anthony
>>
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, January 04, 2013 3:59 PM
> To: Bhushan Bharat-R65777
> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
> Anthony
> Liguori; qemu-devel@nongnu.org qemu-devel
> Subject: Re: [Qemu-dev
Am 04.01.2013 09:35, schrieb q...@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder
> s390-next_x86_64_debian_6_0 while building qemu.
> Full details are available at:
>
> http://buildbot.b1-systems.de/qemu/builders/s390-next_x86_64_debian_6_0/builds/503
>
> Buildbot
On 04.01.2013, at 11:32, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>
> Int timer_func(CPUxxState env)
> {
> Struct timer_regs;
> read_regs_type((env, &timer_regs,TIMER_REGS);
> //update env->timer_registers
> Write_regs_type(env, TIMER_REGS)
> The parameter passing for guest commands was kludgy (list of json
> objects rather than a list of parameter strings), but I think we can handle
> that now with the "gen: no" option to the code parser indicating we'll
> handle it manually.
>
> I'm not sure about the guest-file-open-pipe stuff eith
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, January 04, 2013 4:07 PM
> To: Bhushan Bharat-R65777
> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
> Anthony
> Liguori; qemu-devel@nongnu.org qemu-devel
> Subject: Re: [Qemu-dev
On 04.01.2013, at 12:01, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Friday, January 04, 2013 4:07 PM
>> To: Bhushan Bharat-R65777
>> Cc: Marcelo Tosatti; jjhe...@linux.vnet.ibm.com; Christian Borntraeger;
>> Anthony
>>
Hi,
>> +if (sizeof(time_t) == 32) {
>
> You sure that shouldn't be 4 then?
Oops, yes. Should have waited for buildbot results ...
cheers,
Gerd
Hi,
>> This patch series improves the debug devices we have. isa-debugcon is
>> switched over to the memory api. isa-debug-exit is added and replaces
>> the hard-coded bochs debug port. pc-testdev (used by kvm-unit-tests) is
>> added.
>
> Missing some CCs, and I was actually expecting anothe
Hi Gerd,
Am 04.01.2013 13:57, schrieb Gerd Hoffmann:
>>> This patch series improves the debug devices we have. isa-debugcon is
>>> switched over to the memory api. isa-debug-exit is added and replaces
>>> the hard-coded bochs debug port. pc-testdev (used by kvm-unit-tests) is
>>> added.
>>
>> M
Am 31.12.2012 20:55, schrieb Lucas Meneghel Rodrigues:
> Hmmm, about this one, I'm worried about making things more complex...
>
> The way I see the problem at hand, I'd say if people want to customize
> things, they'd be better of creating their own, specialized config
> files rather than adding
The Buildbot has detected a new failure on builder default_ppc while building
qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds/517
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: qemu-ppc.opensuse.org
Build Reason:
On Fri, Jan 4, 2013 at 6:35 AM, wrote:
> The Buildbot has detected a new failure on builder default_arm_devs_next
> while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/default_arm_devs_next/builds/0
>
> Buildbot URL: http://buildbot.b1-systems.de/
Am 04.01.2013 14:21, schrieb q...@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder default_ppc while building
> qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds/517
>
> Buildbot URL: http://buildbot.b1-systems.de/
Gerd Hoffmann writes:
> Hi,
>
>>> This patch series improves the debug devices we have. isa-debugcon is
>>> switched over to the memory api. isa-debug-exit is added and replaces
>>> the hard-coded bochs debug port. pc-testdev (used by kvm-unit-tests) is
>>> added.
>>
>> Missing some CCs, an
On 04.01.2013, at 14:37, Andreas Färber wrote:
> Am 04.01.2013 14:21, schrieb q...@buildbot.b1-systems.de:
>> The Buildbot has detected a new failure on builder default_ppc while
>> building qemu.
>> Full details are available at:
>> http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds
On 4 January 2013 13:32, Stefan Hajnoczi wrote:
> pm215: Please rebase onto a more recent qemu.git tree to eliminate
> this build failure.
Done. (At the moment the branch is empty of queued patches so it's
the same as git master.)
-- PMM
On Thu, Jan 03, 2013 at 01:50:22PM +0100, Alexander Graf wrote:
>
> On 18.12.2012, at 18:50, Jens Freimann wrote:
>
> > Add a CPU reset handler to have all CPUs in a PoP compliant
> > state.
> >
> > Signed-off-by: Jens Freimann
> >
> > ---
> > v2 -> v3:
> > * remove FIXME
> > * separate parent
The following changes since commit 25bbf61e4bacd1e4fa4115ffcf151051b9d6608e:
pty: unbreak libvirt (2013-01-03 12:53:41 -0600)
are available in the git repository at:
git://github.com/stefanha/qemu.git trivial-patches
for you to fetch changes up to bfb82a28752d29291adf932c3a9941e8383203af:
From: Stefan Weil
sys/mman.h is not needed (tested on Linux) and unavailable for MinGW,
so remove it.
Signed-off-by: Stefan Weil
Signed-off-by: Stefan Hajnoczi
---
hw/spapr_nvram.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/spapr_nvram.c b/hw/spapr_nvram.c
index f2
From: Markus Armbruster
pc_fw_add_pflash_drv() ignores qemu_find_file() failure, and happily
creates a drive without a medium.
When pc_system_flash_init() asks for its size, bdrv_getlength() fails
with -ENOMEDIUM, which isn't checked either. It fails relatively
cleanly only because -ENOMEDIUM i
From: Stefan Weil
This typically reduces the size from 512 bytes to 128 bytes.
Signed-off-by: Stefan Weil
Signed-off-by: Stefan Hajnoczi
---
hw/mcf5206.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/mcf5206.c b/hw/mcf5206.c
index fe7a488..d8c0059 100644
--- a/hw/mcf5
On 01/03/2013 11:02 PM, Wenchao Xia wrote:
>
>>> +# case, it is the internal snapshot record's name
>>> and if it is
>>> +# 'blank' name will be generated according to time.
>>
>> Ugg. Passing an empty string for snapshot-file as a special case seems
>> awkward; i
On 03/01/2013 15:52, fred.kon...@greensocs.com wrote:
+
+static int virtio_blk_pci_init(VirtIOPCIProxy *vpci_dev)
+{
+VirtIOBlkPCI *dev = VIRTIO_BLK_PCI(vpci_dev);
+virtio_blk_set_conf(dev->vdev, &(dev->blk));
+qdev_set_parent_bus(dev->vdev, BUS(vpci_dev->bus));
+if (qdev_init(dev
The spice_server pointer is a global variable and
vm_change_state_handler() therefore does not use its opaque parameter.
The vm change state handler is added with a pointer to the spice_server
pointer. This is useless and we probably would not want 2 levels of
pointers.
Signed-off-by: Stefan Haj
On Thu, Jan 03, 2013 at 01:55:19PM +0100, Alexander Graf wrote:
>
> On 18.12.2012, at 18:50, Jens Freimann wrote:
>
> > Add a CPU reset handler to have all CPUs in a PoP compliant
> > state.
> >
> > Signed-off-by: Jens Freimann
> >
> > ---
> > v2 -> v3:
> > * remove FIXME
> > * separate parent
On 04.01.2013, at 15:09, Jens Freimann wrote:
> On Thu, Jan 03, 2013 at 01:55:19PM +0100, Alexander Graf wrote:
>>
>> On 18.12.2012, at 18:50, Jens Freimann wrote:
>>
>>> Add a CPU reset handler to have all CPUs in a PoP compliant
>>> state.
>>>
>>> Signed-off-by: Jens Freimann
>>>
>>> ---
>
> CCqemu-timer.o
> cc1: warnings being treated as errors
> In file included from
> /home/build/qemu/default_ppc/build/include/ui/qemu-pixman.h:9,
> from
> /home/build/qemu/default_ppc/build/include/ui/console.h:4,
> from qemu-timer.c:27:
> /usr/include/pixman
From: John Spencer
instead use the correct headers that define these functions.
Requested-by: Stefan Weil
Signed-off-by: John Spencer
Reviewed-by: Amos Kong
Reviewed-by: Stefan Weil
Signed-off-by: Stefan Hajnoczi
---
linux-user/syscall.c | 8 +++-
1 file changed, 3 insertions(+), 5 del
On 04.01.2013, at 15:12, Gerd Hoffmann wrote:
>> CCqemu-timer.o
>> cc1: warnings being treated as errors
>> In file included from
>> /home/build/qemu/default_ppc/build/include/ui/qemu-pixman.h:9,
>> from
>> /home/build/qemu/default_ppc/build/include/ui/console.h:4,
>>
On 01/04/2013 11:13 AM, Andreas Färber wrote:
Am 31.12.2012 20:55, schrieb Lucas Meneghel Rodrigues:
Hmmm, about this one, I'm worried about making things more complex...
The way I see the problem at hand, I'd say if people want to customize
things, they'd be better of creating their own, speci
From: 陳韋任 (Wei-Ren Chen)
commit 9b9c37c36439ee0452632253dac7a31897f27f70 always assume sparcv9,
the others are no longer supported. Remove --sparc_cpu option from the
configure list.
Signed-off-by: Chen Wei-Ren
Signed-off-by: Stefan Hajnoczi
---
configure | 1 -
1 file changed, 1 deletion(-
Make for() cycle reusable for the next patch
Signed-off-by: Igor Mammedov
---
v2:
place x86cpu_vendor_words2str() a bit earlier, before feature
arrays to avoid compile error when vendor property is converted
into static property.
---
target-i386/cpu.c | 21 ++---
> > +L2 tables size 64KB is different from
> > +cluster size 4KB.
>
> Umm, doesn't the cluster_bits (bytes 20-23 of the header) determine the
> size of a cluster, rather than assuming a cluster is always 4KB? And
> later on, the spec
On Mon, Dec 17, 2012 at 02:25:04PM +0800, Wenchao Xia wrote:
> This patch moves bdrv_snapshotfind from savevm.c to block.c and export
> it, also added bdrv_deappend in block.c.
I suggest naming the patch "block: export bdrv_snapshot_find()" because
it is more specific than "snapshot: export func
On Thu, 3 Jan 2013, Ian Campbell wrote:
> On Mon, 2012-12-31 at 12:16 +, Roger Pau Monne wrote:
> > Files that reside on ramfs or tmpfs cannot be opened with O_DIRECT,
> > if first call to bdrv_open fails with errno = EINVAL, try a second
> > call without BDRV_O_NOCACHE.
>
> Doesn't that risk
On Mon, Dec 17, 2012 at 02:25:05PM +0800, Wenchao Xia wrote:
This patch has nothing to do with snapshots, so "snapshot: add error set
function" is not a useful commit message. "error: add
error_set_replace()" would be okay. Please use git log on
the file you are modifying to find good component
On 04/01/13 15:54, Stefano Stabellini wrote:
> On Thu, 3 Jan 2013, Ian Campbell wrote:
>> On Mon, 2012-12-31 at 12:16 +, Roger Pau Monne wrote:
>>> Files that reside on ramfs or tmpfs cannot be opened with O_DIRECT,
>>> if first call to bdrv_open fails with errno = EINVAL, try a second
>>> call
On Mon, 31 Dec 2012, Roger Pau Monne wrote:
> On ioreq_release the full ioreq was memset to 0, loosing all the data
> and memory allocations inside the QEMUIOVector, which leads to a
> memory leak. Create a new function to specifically reset ioreq.
>
> Reported-by: Maik Wessler
> Signed-off-by: R
Hi,
> So while I am impartial to this specific patch, some easy way to run a
> comprehensive test coverage without having to manually name each test
> using --tests= would be very handy! Something like --all-tests maybe?
Hint from the dirty tricks department:
--tests=JeOS will do (for --type=
The kvm_mmu_op feature was removed from the kernel since v3.3 (released
in March 2012), it was marked for removal since January 2011 and it's
slower than shadow or hardware assisted paging (see kernel commit
fb92045843). It doesn't make sense to keep it enabled by default.
Also, keeping it enabled
On 4 January 2013 14:59, Gerd Hoffmann wrote:
> Cc: afaer...@suse.de
> Cc: ag...@suse.de
> Signed-off-by: Gerd Hoffmann
> ---
> include/ui/qemu-pixman.h |4
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/ui/qemu-pixman.h b/include/ui/qemu-pixman.h
> index 3c
Cc: afaer...@suse.de
Cc: ag...@suse.de
Signed-off-by: Gerd Hoffmann
---
include/ui/qemu-pixman.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/include/ui/qemu-pixman.h b/include/ui/qemu-pixman.h
index 3c05c83..63b8ccc 100644
--- a/include/ui/qemu-pixman.h
+++ b/inclu
The kvm_mmu_op feature was removed from the kernel since v3.3 (released
in March 2012), it was marked for removal since January 2011 and it's
slower than shadow or hardware assisted paging (see kernel commit
fb92045843). It doesn't make sense to keep it enabled by default.
Also, keeping it enabled
If I've followed the conversation correctly this is what needs to be done:
1. Remove the level parameters from kvm_arch_get_registers and
kvm_arch_put_registers.
2. Add a new bitmap parameter to kvm_arch_get_registers and
kvm_arch_put_registers.
3. Define a bit that correlates to our curren
This is a cleanup that tries to solve two small issues:
- We don't need a separate kvm_pv_eoi_features variable just to keep a
constant calculated at compile-time, and this style would require
adding a separate variable (that's declared twice because of the
CONFIG_KVM ifdef) for each fea
On Fri, 4 Jan 2013, Roger Pau Monne wrote:
> On 04/01/13 15:54, Stefano Stabellini wrote:
> > On Thu, 3 Jan 2013, Ian Campbell wrote:
> >> On Mon, 2012-12-31 at 12:16 +, Roger Pau Monne wrote:
> >>> Files that reside on ramfs or tmpfs cannot be opened with O_DIRECT,
> >>> if first call to bdrv_
Running qemu-img commit on QED image emits the below message even if the
image is never committed. This patch fixes this. Do we need to do any
L1, L2 table cleanup here ? I see that cleanup code is commented out in
the case of qcow2 (qcow2_make_empty).
before patching -
# qemu-img commit -f qed s
Now that all entries have check_feat=~0 on
kvm_check_features_against_host(), we can eliminate check_feat entirely
and make the code check all bits.
This patch shouldn't introduce any behavior change, as check_feat is set
to ~0 on all entries.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.
This adds the following feature words to the list of flags to be checked
by kvm_check_features_against_host():
- cpuid_7_0_ebx_features
- ext4_features
- kvm_features
- svm_features
This will ensure the "enforce" flag works as it should: it won't allow
QEMU to be started unless every flag tha
The -cpu check/enforce warnings are printing incorrect information about the
missing flags. There are no feature flags on CPUID leaves 0 and 0x8000, but
there were references to 0 and 0x8000 in the table at
kvm_check_features_against_host().
This changes the model_features_t struct to cont
On Mon, Dec 17, 2012 at 02:25:09PM +0800, Wenchao Xia wrote:
> @@ -983,17 +983,22 @@ ETEXI
>
> {
> .name = "snapshot_blkdev",
> -.args_type = "reuse:-n,device:B,snapshot-file:s?,format:s?",
> -.params = "[-n] device [new-image-file] [format]",
> -.
Hi,
>> +/* pixman-0.16.0 headers have a redundant declaration */
>> +#pragma GCC diagnostic push
>> +#pragma GCC diagnostic ignored "-Wredundant-decls"
>> #include
>> +#pragma GCC diagnostic pop
>
> IIRC we can't rely on gcc knowing about 'diagnostic push/pop' --
> eg in coroutine-ucontext.c
On Fri, Jan 04, 2013 at 03:25:36PM +0100, Igor Mammedov wrote:
> Make for() cycle reusable for the next patch
>
> Signed-off-by: Igor Mammedov
> ---
> v2:
> place x86cpu_vendor_words2str() a bit earlier, before feature
> arrays to avoid compile error when vendor property is converted
>
The existing -cpu host code simply set every bit inside svm_features
(initializing it to -1), and that makes it impossible to make the
enforce/check options work properly when the user asks for SVM features
explicitly in the command-line.
So, instead of initializing svm_features to -1, use GET_SUP
This changes the -cpu check/enforce code to work as it should: it will
check every single CPUID bit to make sure it is supported by the host.
The changes are a bit intrusive, but:
- The longer we take to make "enforce" strict as it should (and make libvirt
finally use it), more users will hav
This will be necessary once kvm_check_features_against_host() starts
using KVM-specific definitions (so it won't compile anymore if
CONFIG_KVM is not set).
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-i386/cpu.c b/target-i386
When nested SVM is supported, the kernel returns the SVM flag on
GET_SUPPORTED_CPUID[1], so we can check the SVM flag safely on
kvm_check_features_against_host().
I don't know why the original code ignored the SVM flag. Maybe it was
because kvm_cpu_fill_host() used the CPUID instruction directly i
We don't need any hack to ignore CPUID_EXT_HYPERVISOR anymore, because
kvm_arch_get_supported_cpuid() now set CPUID_EXT_HYPERVISOR properly.
So, this shouldn't introduce any behavior change, but it makes the code
simpler.
Signed-off-by: Eduardo Habkost
---
My goal is to eliminate the check_feat f
When using -cpu host, we don't need to use the kvm_default_features
variable, as the user is explicitly asking QEMU to enable all feature
supported by the host.
This changes the kvm_cpu_fill_host() code to use GET_SUPPORTED_CPUID to
initialize the kvm_features field, so we get all host KVM feature
I have no idea why PPRO_FEATURES was being ignored on the check of the
CPUID.8001H.EDX bits. I believe it was a mistake, and it was
supposed to be ~(PPRO_FEATURES & CPUID_EXT2_AMD_ALIASES) or just
~CPUID_EXT2_AMD_ALIASES, because some time ago kvm_cpu_fill_host() used
the CPUID instruction dire
On 01/03/2013 07:28:49 PM, Bhushan Bharat-R65777 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Friday, January 04, 2013 1:51 AM
> To: Bhushan Bharat-R65777
> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org; ag...@suse.de;
Bhushan Bharat-
> R65777
> Subject: Re: [Qemu-p
On Fri, Dec 21, 2012 at 06:20:40AM +, Dietmar Maurer wrote:
> >If libvirt could integrate external tool using code, that would be
> > great. For
> > qemu, My understanding is just to take internal snapshot and stop vm,
>
> You just need to save VM state, flush all IO requests, then stop.
On 12/18/2012 05:41 AM, Vasilis Liaskovitis wrote:
> Returns total physical memory available to guest in bytes, including
> hotplugged
> memory. Note that the number reported here may be different from what the
> guest
> sees e.g. if the guest has not logically onlined hotplugged memory.
>
> Thi
On Mon, Dec 17, 2012 at 02:25:08PM +0800, Wenchao Xia wrote:
> @@ -1478,16 +1497,39 @@
> #
> # @device: the name of the device to generate the snapshot from.
> #
> -# @snapshot-file: the target of the new image. A new file will be created.
> +# @snapshot-file: the target name of the snapshot. I
On 04.01.2013, at 16:25, Jason J. Herne wrote:
> If I've followed the conversation correctly this is what needs to be done:
>
> 1. Remove the level parameters from kvm_arch_get_registers and
> kvm_arch_put_registers.
>
> 2. Add a new bitmap parameter to kvm_arch_get_registers and
> kvm_arch_p
On Thu, Jan 03, 2013 at 09:43:53PM +0800, Liu Yuan wrote:
> On 12/25/2012 04:45 PM, Liu Yuan wrote:
> > Well, I found setting cache=directsync will contain 'BDRV_O_CACHE_WB'.
> > Is this a bug for current master? If no, my current scheme will be the
> > only way to bypass cache of sheepdog.
>
> Pi
On Mon, 31 Dec 2012, Roger Pau Monne wrote:
> This protocol extension reuses the same set of grant pages for all
> transactions between the front/back drivers, avoiding expensive tlb
> flushes, grant table lock contention and switches between userspace
> and kernel space. The full description of th
On Mon, Dec 31, 2012 at 08:46:45PM -, Christopher Mason wrote:
> Public bug reported:
>
> I'm seeing consistent hangs / crashes on MacOS 10.8.2 with 1.3.0. I've
> tried both gcc-4.2 and clang. I've tried a half a dozen different
> images/kernels.
Which QEMU version are you building? Have y
On Wed, Jan 02, 2013 at 12:07:57PM -0600, Anthony Liguori wrote:
> Over the holiday, I spent some time overhauling my patch tracking
> scripts. One new feature is automated responses so you will start
> seeing some additional mail on the list. Notably:
>
> 1) My 'Thanks, applied.' mails are no
On 12/29/2012 01:45 AM, Wenchao Xia wrote:
> This patch moves collect_image_info() and collect_snapshot()
> to general block layer and encapsulate them as bdrv_query_image_info()
> and bdrv_query_snapshot_infolist(), as mirror function to brdv_query_info().
> The called function in qemu-img.c is
Running qemu-img commit on QED image gives this message even if the
image is never committed. This patch fixes this. Do we need to do any
L1, L2 table cleanup here ? I see that cleanup code is commented out in
the case of qcow2 (qcow2_make_empty).
before patching -
# qemu-img commit -f qed ss.qed
1 - 100 of 217 matches
Mail list logo
