Hi Liuis,
On Tue, Sep 04, 2012 at 10:08:09PM +0200, Lluís Vilanova wrote:
> Hi there,
>
> Given that right now I don't have enough time to write the paper that should
> accompany this work, I've decided to open it up so that whoever is interested
> can have access to it.
>
> You can get some ins
On 09/20/12 17:33, Stefano Stabellini wrote:
> On Thu, 20 Sep 2012, Stefano Stabellini wrote:
>> On Thu, 20 Sep 2012, Gerd Hoffmann wrote:
>>> Hi,
>>>
> In any graphics mode relevant today vga emulation will use
> qemu_create_displaysurface_from(). Whenever a DisplayAllocator is
> pr
Hi Alex, Juan,
I know Juan has an outstanding patch that converts target-ppc to use
the new VMStateDescription approach for savevm at
http://lists.gnu.org/archive/html/qemu-devel/2012-05/msg00532.html
Before I noticed that patch was out there, I had done my own
conversion (patch below) using a d
In the paravirtualized environment provided by PAPR, there is a standard
locking scheme so that hypercalls updating the hash page table from
different guest threads don't corrupt the haah table state. We implement
this HVLOCK bit in out page table hypercalls. However, it is not necessary
in our c
On Thu, Sep 20, 2012 at 05:08:56PM +0200, Paolo Bonzini wrote:
>
> Just shooting around a possibility: why reinvent the wheel poorly if we
> can use a full-blown URI parsing library? The libxml2 one is very good
> and easy to use.
>
> It is also pretty much self-contained and has hardly seen a c
Alex,
If you think these patches are ready, I'll certain be happy to see
them applied. However, I suspect you (and/or others) will have
comments on how they're implemented, particularly 2-4. If so, I hope
to get those as soon as convenient so I can revise as necessary well
before the next releas
This patch adds some extra FPU state to CPUPPCState. Specifically, fpscr
is extended to 64 bits, since some recent CPUs now have more status bits
than fit inside 64 bits, and we add the 32 VSR registers present on CPUs
with VSX (these extend the standard FP regs, which together with the
Altivec/VM
CPUPPCState includes a variable 'power_mode' which is used nowhere. This
patch removes it. This includes saving a dummy zero in its place during
vmsave, to avoid breaking the save format.
Signed-off-by: David Gibson
---
target-ppc/cpu.h |1 -
target-ppc/machine.c |4 ++--
2 files c
Currently the pseries machine code always attempts to set the size of the
guests's hash page table to 16MB. However, because of the way the POWER
MMU works, a suitable hash page table size should really depend on memory
size. 16MB will be excessive for guests with <1GB and RAM, and may not be
eno
Below is a patch which implements the (PAPR mandated) NVRAM for the
pseries machine. It raises a couple of generic questions.
First, this adds a new "nvram" machine option which is used to give a
block device id to back the NVRAM so it is persistent. Since some
sort of NVRAM is quite common, it
On Thu, Sep 20, 2012 at 02:44:26PM +0200, Alexander Graf wrote:
>
> On 20.09.2012, at 13:53, David Gibson wrote:
>
> > On Thu, Sep 20, 2012 at 09:38:58AM +0200, Alexander Graf wrote:
> >>
> >> On 20.09.2012, at 09:08, David Gibson wrote:
> >>
> >>> Currently the KVM exit path for PAPR hypercall
See
http://lists.nongnu.org/archive/html/qemu-devel/2012-09/msg03196.html
for the whole story.
Signed-off-by: Max Filippov
---
tcg/README |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/tcg/README b/tcg/README
index cfdfd96..86b43f1 100644
--- a/tcg/README
+++ b/tcg/RE
Do a sanity checking pass on the intermediate code.
Check that goto_tb indices are either 0 or 1 and used at most once per
TB.
Signed-off-by: Max Filippov
---
tcg/tcg.c | 69 +
1 files changed, 69 insertions(+), 0 deletions(-)
diff -
Does this look sane or should it better be merged with e.g. tcg_dump_ops?
Max Filippov (2):
tcg/README: document tcg_gen_goto_tb restrictions
tcg: add TB sanity checking
tcg/README |3 +-
tcg/tcg.c | 69
2 files changed, 71
On Thursday, September 20, 2012 07:29:08 PM Shawn Starr wrote:
> On Thursday, September 20, 2012 05:37:44 PM Hans de Goede wrote:
> > Hi,
> >
> > On 09/19/2012 06:42 PM, Shawn Starr wrote:
> > > Hello QMU folks,
> > >
> > > The latest EHCI patches and or USB redirection ones have caused a
> > > r
On 09/20/2012 03:59 PM, Max Filippov wrote:
> +if (shiftimm) {
> +tcg_gen_shri_i32(tmp, cpu_R[RRR_T], shiftimm);
> +} else {
> +tcg_gen_mov_i32(tmp, cpu_R[RRR_T]);
> +}
tcg_gen_shri_i32 will perform this condit
On Thursday, September 20, 2012 05:37:44 PM Hans de Goede wrote:
> Hi,
>
> On 09/19/2012 06:42 PM, Shawn Starr wrote:
> > Hello QMU folks,
> >
> > The latest EHCI patches and or USB redirection ones have caused a
> > regression. Using the (legacy) qemu-kvm git master repository which does
> > not
If readonly=on is given at device creation time, the ->readonly flag
needs to be set in the block driver state for this device so that
readonly-ness is preserved across media changes (qmp change command).
Similarly, to preserve the snapshot property requires ->open_flags to
be correct.
Signed-off-
On Fri, 21 Sep 2012, Max Filippov wrote:
> Max Filippov (2):
> target-xtensa: fix extui shift amount
> target-xtensa: don't emit extra tcg_gen_goto_tb
>
> target-xtensa/translate.c | 28
> 1 files changed, 24 insertions(+), 4 deletions(-)
>
Applied, thanks.
Unconditional gen_check_loop_end at the end of disas_xtensa_insn
can emit tcg_gen_goto_tb with slot id already used in the TB (e.g. when
TB ends at LEND with a branch).
Signed-off-by: Max Filippov
Cc: qemu-stable
---
target-xtensa/translate.c |4 +++-
1 files changed, 3 insertions(+), 1 del
extui opcode only uses lowermost op1 bit for sa4.
Reported-by: malc
Signed-off-by: Max Filippov
Cc: qemu-stable
---
target-xtensa/translate.c | 24 +---
1 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/target-xtensa/translate.c b/target-xtensa/translate.c
i
Max Filippov (2):
target-xtensa: fix extui shift amount
target-xtensa: don't emit extra tcg_gen_goto_tb
target-xtensa/translate.c | 28
1 files changed, 24 insertions(+), 4 deletions(-)
--
1.7.7.6
On Thu, 20 Sep 2012, Max Filippov wrote:
> On Wed, Sep 19, 2012 at 11:53 PM, Richard Henderson wrote:
> > On 09/19/2012 11:30 AM, Peter Maydell wrote:
> >> ...but on the other hand that ought to work for PPC too, so
> >> presumably my analysis is wrong somewhere.
> >
> > It isn't. It's a target-
On 09/20/2012 03:06 PM, Aurelien Jarno wrote:
>> > +if (TCG_TARGET_HAS_movcond_i64) {
>> > +tcg_gen_op6i_i64(INDEX_op_movcond_i64, ret, c1, c2, v1, v2, cond);
>> > +return;
> Minor nitpick: there is useless return here, and it's not present for
> movcond_i32.
>
Ah, right. I s
On Tue, Sep 18, 2012 at 07:23:56AM -0700, Richard Henderson wrote:
> Implemented with setcond if the target does not provide
> the optional opcode.
>
> Signed-off-by: Richard Henderson
> ---
> tcg/README | 6 ++
> tcg/arm/tcg-target.h | 1 +
> tcg/hppa/tcg-target.h | 1 +
>
On Tue, Sep 18, 2012 at 11:11:48PM +0200, Aurelien Jarno wrote:
> On Tue, Sep 18, 2012 at 07:23:59AM -0700, Richard Henderson wrote:
> > Signed-off-by: Richard Henderson
> > ---
> > tcg/optimize.c | 29 +
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/tcg/o
Seccomp syscall whitelist updated after tests running qemu under
libvirt. Reference to the bug -
https://bugzilla.redhat.com/show_bug.cgi?id=855162
Regards,
---
qemu-seccomp.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
On 09/20/2012 01:17 AM, Dave Young wrote:
> For virtio block device, if user does not specify the serial attribute,
> There will be not serial availabe, this is not convinient for identify
s/not serial availabe/no serial available/
s/convinient/convenient/
s/identify/identifying/
> the disk.
>
>
Oops, local mta use wrong from line, should use below:
From: Dave Young
On 09/20/2012 04:48 PM, Dave Young wrote:
> For virtio block device, if user does not specify the serial attribute,
> There will be not serial availabe, this is not convinient for identify
> the disk.
>
> Doing something si
For virtio block device, if user does not specify the serial attribute,
There will be not serial availabe, this is not convinient for identify
the disk.
Doing something similar to ide disks, add a "VD?" default serial
number if user does not specify it.
Signed-off-by: Dave Young
---
hw/virt
Also known as Paravirtualization CPUIDs.
This is primarily done so that the guest will think it is running
under vmware when hypervisor-vendor=vmware is specified as a
property of a cpu.
This depends on:
http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg01400.html
As far as I know it is
Signed-off-by: Don Slutz
---
target-i386/cpu.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index 6dafaeb..e158c54 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -807,6 +807,10 @@ typedef struct CPUX86State {
uin
On Thu, 20 Sep 2012 15:42:30 +0800
Lei Li wrote:
> On 09/20/2012 02:05 AM, Luiz Capitulino wrote:
> > On Wed, 12 Sep 2012 19:57:24 +0800
> > Lei Li wrote:
> >
> >> Signed-off-by: Lei Li
> >> ---
> >> hmp-commands.hx | 23 ++
> >> hmp.c| 19 +++
> >
Fix duplicate name (kvmclock => kvm_clock2) also.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 0313cf5..5f9866a 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
The check using INT_MAX (2147483647) is wrong in this case.
Signed-off-by: Fred Oliveira
Signed-off-by: Don Slutz
---
target-i386/cpu.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index af50a8f..0313cf5 100644
--- a/target-i386
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
Signed-off-by: Luiz Capitulino
---
dump.c | 3 +--
migration-fd.c | 2 +-
monitor.c | 15 +--
monitor.h | 2 +-
4 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/dump.c b/dump.c
index 2bf8d8d..1a3c
These are the stubs for the file reopen drivers for the qcow2 format.
There is currently nothing that needs to be done by the qcow2 driver
in reopen.
Signed-off-by: Jeff Cody
---
block/qcow2.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/block/qcow2.c b/block/qcow2.c
index 8f
These are modeled after x86_cpuid_set_vendor and x86_cpuid_get_vendor.
Since kvm's vendor is shorter, the test for correct size is removed and zero
padding is added.
Set Microsoft's Vendor now that we can. Value defined in:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v
On 09/20/2012 12:18 PM, Luiz Capitulino wrote:
> Before the qapi conversion, the sendkey command could be used to
> send key codes in hex directly to the guest. This doesn't work
> with the current implemention, as it will only send to the guest
> QKeyCode values. That's a regression.
>
> This com
This was taken from:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/22643
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 7e9c43b..459469
Also known as Paravirtualization vendor.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Al
This is used to set the cpu object's hypervisor level to the default for
Microsoft's Hypervisor.
HYPERV_CPUID_MIN (0x4005) is defined in a linux header file.
CPUID_HV_LEVEL_HYPERV (0x4005) is used instead.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 10 ++
target-i386/cp
HI all,
I reported this bug ion launchpad, but it never seemed to show up
here on the list:
https://bugs.launchpad.net/qemu/+bug/1052857
Anyone have any clues on what's going on here?
Erik
--
--
Erik de Castro Lopo
http://
Also known as Paravirtualization vendor.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Al
Also fixes a few issues while there:
1. The fd returned by monitor_get_fd() leaks in most error conditions
2. monitor_get_fd() return value is not checked. Best case we get
an error that is not correctly reported, worse case one of the
functions using the fd (with value of -1) will explo
From: Paolo Bonzini
There is no need to open-code the choice between a file descriptor
number or a named one. Just use monitor_handle_fd_param, which
also takes care of printing the error message.
Signed-off-by: Paolo Bonzini
Signed-off-by: Luiz Capitulino
---
hw/kvm/pci-assign.c | 12 +++---
The first two patches work on adding an Error * argument to monitor_get_fd().
The second patch is the actual conversion of add_client.
v2
o add Error * argument to monitor_get_fd()
o fix schema doc mistakes
dump.c | 3 +--
hw/kvm/pci-assign.c | 12 +++-
migration-fd.c
Code motion, to move parsing of open flags into a helper function.
Signed-off-by: Jeff Cody
---
block/raw-posix.c | 38 --
block/raw-win32.c | 43 +++
2 files changed, 47 insertions(+), 34 deletions(-)
diff --git a/bloc
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Als
These are the stubs for the file reopen drivers for the qcow format.
There is currently nothing that needs to be done by the qcow driver
in reopen.
Signed-off-by: Jeff Cody
---
block/qcow.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/block/qcow.c b/block/qcow.c
index 7b5ab87
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 66 +
1 files changed, 66 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 904b08f..7e9c43b 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1273
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 4594693..72a8442 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1991,6 +1991,17 @@ void cpu_x86_cpuid(CPUX86St
Also known as Paravirtualization vendor.
This is EBX, ECX, EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel chang
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 5f9866a..0e4a18d 100644
--- a/tar
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 44 +++-
target-i386/cpu.h | 14 ++
2 files changed, 57 insertions(+), 1 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 5cf7146..904b08f 100644
--- a/target-i386/cpu.c
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Als
Also known as Paravirtualization level or maximim cpuid function present in
this leaf.
This is just the EAX value for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware
Signed-off-by: Don Slutz
---
target-i386/kvm.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index dde9214..bd7753f 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -457,6 +457,25 @@ int kvm_arch_init_vcp
The keep_read_only flag is no longer used, in favor of the bdrv
flag BDRV_O_ALLOW_RDWR.
Signed-off-by: Jeff Cody
---
block.c | 2 --
block_int.h | 1 -
2 files changed, 3 deletions(-)
diff --git a/block.c b/block.c
index 84544d2..751ebdc 100644
--- a/block.c
+++ b/block.c
@@ -812,8 +812,6 @
Block drivers should ignore BDRV_O_CACHE_WB in .bdrv_open flags,
and in the bs->open_flags.
This patch removes the code, leaving the behaviour behind as if
BDRV_O_CACHE_WB was set.
Signed-off-by: Jeff Cody
---
block/iscsi.c | 4
block/raw-posix.c | 3 ---
block/raw-win32.c | 3 ---
This patch supports reopen for VMDK image files. VMDK extents are added
to the existing reopen queue, so that the transactional model of reopen
is maintained with multiple image files.
Signed-off-by: Jeff Cody
---
block/vmdk.c | 35 +++
1 file changed, 35 inserti
This is derived from the Supriya Kannery's reopen patches.
This contains the raw-posix driver changes for the bdrv_reopen_*
functions. All changes are staged into a temporary scratch buffer
during the prepare() stage, and copied over to the live structure
during commit(). Upon abort(), all chang
>From http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html
EAX should be KVM_CPUID_FEATURES (0x4001) not 0.
Added hypervisor-vendor=kvm0 to get the older CPUID result. kvm1 selects the
newer one.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 17 +
1 files c
Looking at http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html
The new value for EAX is 0x4001.
This depends on
http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg02497.html
As far as I known it is #5. It depends on (1), (2), (3) and (4).
Based on cpu-queue[1] branch.
(Fr
These patches are based off Supriya Kannery's original bdrv_reopen()
patches as part of the hostcache series.
This provides support for safe reopen of a single image, or transactional
reopening of multiple images atomically.
These changes are all reflected in my github repo:
git://github.com
Rather than check for a non-NULL aligned_buf to determine if
raw_aio_submit needs to check for alignment, check for the presence
of BDRV_O_NOCACHE in the bs->open_flags.
Signed-off-by: Jeff Cody
---
block/raw-posix.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/raw-p
These are the stubs for the file reopen drivers for the qed format.
There is currently nothing that needs to be done by the qed driver
in reopen.
Signed-off-by: Jeff Cody
---
block/qed.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/block/qed.c b/block/qed.c
index 21cb239..6c182c
There is currently nothing that needs to be done for VDI reopen.
Signed-off-by: Jeff Cody
---
block/vdi.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/block/vdi.c b/block/vdi.c
index 550cf58..f35b12e 100644
--- a/block/vdi.c
+++ b/block/vdi.c
@@ -454,6 +454,12 @@ static int vdi_ope
This is the support for reopen, for win32. Note that there is a key
difference in the win32 reopen, namely that it is not guaranteed safe
like all the other drivers. Attempts are made to reopen the file, or
open the file in a new handle prior to closing the old handle. However,
this is not alway
These are the stubs for the file reopen drivers for the raw format.
There is currently nothing that needs to be done by the raw driver
in reopen.
Signed-off-by: Jeff Cody
---
block/raw.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/block/raw.c b/block/raw.c
index ff34ea4..253
The aligned_buf pointer and aligned_buf size are no longer used in
raw_posix.c, so remove all references to them.
Signed-off-by: Jeff Cody
---
block/raw-posix.c | 21 +
1 file changed, 1 insertion(+), 20 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index 1
Currently, bdrv_commit() reopens images r/w itself, via risky
_delete() and _open() calls. Use the new safe method for drive reopen.
Signed-off-by: Jeff Cody
---
block.c | 48 +---
1 file changed, 5 insertions(+), 43 deletions(-)
diff --git a/block.c
I believe the bs->keep_read_only flag is supposed to reflect
the initial open state of the device. If the device is initially
opened R/O, then commit operations, or reopen operations changing
to R/W, are prohibited.
Currently, the keep_read_only flag is only accurate for the active
layer, and its
Add a type cast which was removed by commit
213fd5087e2e4e2da10ad266df0ba950cf7618bf again.
Without it, MinGW compilers complain:
net/socket.c:136: warning:
pointer targets in passing argument 2 of ‘sendto’ differ in signedness
/usr/lib/gcc/amd64-mingw32msvc/4.4.4/../../../../amd64-mingw32msvc/i
This is based on Supriya Kannery's bdrv_reopen() patch series.
This provides a transactional method to reopen multiple
images files safely.
Image files are queue for reopen via bdrv_reopen_queue(), and the
reopen occurs when bdrv_reopen_multiple() is called. Changes are
staged in bdrv_reopen_pre
There is currently nothing that needs to be done for VPC image
file reopen.
Signed-off-by: Jeff Cody
---
block/vpc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/block/vpc.c b/block/vpc.c
index c0b82c4..b6bf52f 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -265,6 +265,12 @@ static
Move AIO initialization for raw-posix block driver into a helper function.
In addition to just code motion, the aio_ctx pointer is checked for NULL,
prior to calling laio_init(), to make sure laio_init() is only run once.
Signed-off-by: Jeff Cody
---
block/raw-posix.c | 53 +
bdrv_set_enable_write_cache() sets the bs->enable_write_cache flag,
but without the flag recorded in bs->open_flags, then next time
a reopen() is performed the enable_write_cache setting may be
inadvertently lost.
This will set the flag in open_flags, so it is preserved across
reopens.
Signed-off
On Thursday, September 20, 2012 05:37:44 PM Hans de Goede wrote:
> Hi,
>
> Thanks for reporting this. This is caused by a recent change to
> fix a memory leak inside the ehci codes interrupt ep handling, together
> with:
>
> // TODO Windows does not seem to ever set the MULT field
>
> The a
On 09/20/2012 10:04 AM, Mel Gorman wrote:
This is almost entirely based on Rik's previous patches and discussions
with him about how this might be implemented.
Order > 0 compaction stops when enough free pages of the correct page
order have been coalesced. When doing subsequent higher order all
On 09/20/2012 10:04 AM, Mel Gorman wrote:
When compaction was implemented it was known that scanning could potentially
be excessive. The ideal was that a counter be maintained for each pageblock
but maintaining this information would incur a severe penalty due to a
shared writable cache line. It
On 09/20/2012 10:04 AM, Mel Gorman wrote:
This reverts commit 7db8889a (mm: have order > 0 compaction start off
where it left) and commit de74f1cc (mm: have order > 0 compaction start
near a pageblock with free pages). These patches were a good idea and
tests confirmed that they massively reduced
On 09/20/2012 10:04 AM, Mel Gorman wrote:
Compactions free scanner acquires the zone->lock when checking for PageBuddy
pages and isolating them. It does this even if there are no PageBuddy pages
in the range.
This patch defers acquiring the zone lock for as long as possible. In the
event there a
On 09/20/2012 10:04 AM, Mel Gorman wrote:
Compactions migrate scanner acquires the zone->lru_lock when scanning a range
of pages looking for LRU pages to acquire. It does this even if there are
no LRU pages in the range. If multiple processes are compacting then this
can cause severe locking cont
On 09/20/2012 10:04 AM, Mel Gorman wrote:
From: Shaohua Li
Changelog since V2
o Fix BUG_ON triggered due to pages left on cc.migratepages
o Make compact_zone_order() require non-NULL arg `contended'
Changelog since V1
o only abort the compaction if lock is contended or run too long
o Rearrange
The hex key conversion is unused since last commit.
Signed-off-by: Luiz Capitulino
---
input.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/input.c b/input.c
index 187a131..da3ed27 100644
--- a/input.c
+++ b/input.c
@@ -186,8 +186,7 @@ static const int key_d
The current code duplicates the QKeyCodeList keys in order to store
the key values for release_keys() late run. This is a bit complicated
though, as we have to care about correct ordering and then release_keys()
will have to index key_defs[] over again.
Switch to an array of integers, which is dyn
Before the qapi conversion, the sendkey command could be used to
send key codes in hex directly to the guest. This doesn't work
with the current implemention, as it will only send to the guest
QKeyCode values. That's a regression.
This commit fixes the problem by adding hex value support down
the
This actually fixes a regression introduced by the qapi conversion,
please refer to patch 2/3 for details.
It's also important to note that this series changes the QMP
interface for the send-key command, but this shouldn't be a problem
as we're still in development phase.
hmp.c| 43 +
Hi,
a regression test of CVE-2011-1751 (fixed by
505597e4476a6bc219d0ec1362b760d71cb4fdca) found that when writing 2 to
0xae08, qemu-system-i386 crashes with
ERROR:qom/object.c:386:object_finalize: assertion failed: (obj->ref == 0)
A simple way to reproduce this (in qemu 1.1 or 1.2) is:
serge@u
Am 05.09.2012 19:45, schrieb Stefan Weil:
Am 05.09.2012 19:15, schrieb Stefan Weil:
AFAIK, binutils moved to GPL 3. Therefore I don't expect that
QEMU will update to upstream in the next years.
We'll have to maintain the code which we have.
Try "git log *-dis.c" or "gitk *-dis.c": there are a
Am 01.09.2012 13:00, schrieb Stefan Weil:
Report from smatch:
hw/pflash_cfi01.c:431 pflash_write(180) info: ignoring unreachable code.
Instead of removing the return statement after the switch statement,
the patch replaces the return statements in the switch statement by
break statements. Other
Am 01.09.2012 09:40, schrieb Stefan Weil:
The old code leaks variable 'peer'.
Signed-off-by: Stefan Weil
---
qemu-sockets.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Report from smatch:
qemu-sockets.c:404 inet_dgram_opts(101) warn: variable dereferenced before
check 'peer' (s
Hi guys,
We're seeing the following problem during upstream testing:
qemu: VQ 0 size 0x80 Guest index 0x2d6
inconsistent with Host index 0x18: delta 0x2be
qemu: warning: error while loading state for
instance 0x0 of device ':00:04.0/virtio-blk'
load of migration failed
This
On Wed, Sep 19, 2012 at 05:26:01PM -0400, Don Slutz wrote:
> On 09/19/12 15:32, Eduardo Habkost wrote:
> >On Mon, Sep 17, 2012 at 10:00:55AM -0400, Don Slutz wrote:
> >>This is used to set the cpu object's hypervisor level to the default for
> >>Microsoft's Hypervisor.
> >>
> >>Signed-off-by: Don
There are several issues with our handling of the MULT epcap field
of interrupt qhs, which this patch fixes.
1) When we don't execute a transaction because of the transaction counter
being 0, p->async stays EHCI_ASYNC_NONE, and the next time we process the
same qtd we hit an assert in ehci_state_f
Hi,
On 09/19/2012 06:42 PM, Shawn Starr wrote:
Hello QMU folks,
The latest EHCI patches and or USB redirection ones have caused a regression.
Using the (legacy) qemu-kvm git master repository which does
not have these patches (not sure which patch is causing assert specifically
yet). Using a
On Thu, 20 Sep 2012, Stefano Stabellini wrote:
> On Thu, 20 Sep 2012, Gerd Hoffmann wrote:
> > Hi,
> >
> > >> In any graphics mode relevant today vga emulation will use
> > >> qemu_create_displaysurface_from(). Whenever a DisplayAllocator is
> > >> present or not doesn't make any difference the
On Thu, 20 Sep 2012, Gerd Hoffmann wrote:
> Hi,
>
> >> In any graphics mode relevant today vga emulation will use
> >> qemu_create_displaysurface_from(). Whenever a DisplayAllocator is
> >> present or not doesn't make any difference then.
> >
> > Unfortunately if my memory doesn't fail me, Win
Hi,
>> In any graphics mode relevant today vga emulation will use
>> qemu_create_displaysurface_from(). Whenever a DisplayAllocator is
>> present or not doesn't make any difference then.
>
> Unfortunately if my memory doesn't fail me, Windows uses 24 bpp.
> So actually the DisplayAllocator int
1 - 100 of 209 matches
Mail list logo
