08.05.2013 13:46, Trival wrote:
Signed-off-by: Trival triv...@linux.vnet.ibm.com
---
block/nbd.c | 2 +-
fsdev/virtfs-proxy-helper.c | 4 ++--
hw/9pfs/virtio-9p-local.c | 2 +-
hw/i386/pc_q35.c| 2 +-
hw/intc/imx_avic.c | 2 +-
hw/usb/host-linux.c
Michael Tokarev m...@tls.msk.ru writes:
08.05.2013 13:46, Trival wrote:
Signed-off-by: Trival triv...@linux.vnet.ibm.com
Something went wrong in sending this. This is not a valid SoB.
Regards,
Anthony Liguori
---
block/nbd.c | 2 +-
fsdev/virtfs-proxy-helper.c | 4 ++--
When running an L=1 cmp instruction on a 64bit PPC CPU with SF off, it
still behaves identical to what it does when SF is on. Remove the implicit
difference in the code.
However, the situation is more complex than that. On 32bit CPUs, L=1
instructions are either treated identical to L=0
On 2013-05-08 06:07, Alexander Graf wrote:
When running a 32bit target CPU with qemu-(system-)-ppc, NARROW_MODE
is not set, so we never get to leverage the 32bit only code path in
the compare op handlers.
Introduce new handlers based on the 32bit only flag. That way we can
have 2 separate
On 2013-05-08 06:07, Alexander Graf wrote:
Some instructions behave differently depending on whether the CPU is
64bit capable or not, regardless of the mode the CPU is in.
Add a new instruction flag that indicates that we're running on a CPU
that can not execute 64bit code.
Signed-off-by:
On 2013-05-08 08:26, Alexander Graf wrote:
However, the situation is more complex than that. On 32bit CPUs, L=1
instructions are either treated identical to L=0 instructions (G4) or
treated as illegal instructions (e500mc). Differenciating these cases
is out of scope for the 1.5 release and will
---
hw/misc/zynq_slcr.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/hw/misc/zynq_slcr.c b/hw/misc/zynq_slcr.c
index 8418327..e88702e 100644
--- a/hw/misc/zynq_slcr.c
+++ b/hw/misc/zynq_slcr.c
@@ -396,6 +396,9 @@ static void zynq_slcr_write(void *opaque, hwaddr
Am 29.04.2013 um 09:42 hat Stefan Hajnoczi geschrieben:
@block-backup
Start a point-in-time copy of a block device to a new destination. The
status of ongoing block backup operations can be checked with
query-block-jobs. The operation can be stopped before it has completed using
the
Public bug reported:
The QEMU Gtk+ frontend fails to build..
cc -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg
-I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg/i386 -I.
-I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0
-I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/include -Iui
On Wed, May 08, 2013 at 01:43:22PM +0800, li guang wrote:
ping ...
I guess this didn't get any attention because we were already past soft
freeze, and the focus was to get important features/fixes in shape
before hard freeze.
I don't think I can review it because I never worked on the TCG code.
Alexander Graf ag...@suse.de writes:
Reported-by: Torbjorn Granlund t...@gmplib.org
Signed-off-by: Alexander Graf ag...@suse.de
Ah, so my original patch was correct after all.
Only the name of the author needed changing, apparently. :-)
---
target-ppc/translate.c |8
1
On 08.05.2013, at 15:49, Torbjorn Granlund wrote:
Alexander Graf ag...@suse.de writes:
Reported-by: Torbjorn Granlund t...@gmplib.org
Signed-off-by: Alexander Graf ag...@suse.de
Ah, so my original patch was correct after all.
Only the name of the author needed changing, apparently.
From: Petar Jovanovic petar.jovano...@imgtec.com
The emulator needs to check in hflags if DSP unit has been turned off before
it generates code for MUL_PH, MUL_S_PH, MULQ_S_W, and MULQ_RS_W.
Signed-off-by: Petar Jovanovic petar.jovano...@imgtec.com
---
target-mips/translate.c |1 +
1 file
On Wed, May 08, 2013 at 03:26:00PM +0200, Alexander Graf wrote:
When running an L=1 cmp instruction on a 64bit PPC CPU with SF off, it
still behaves identical to what it does when SF is on. Remove the implicit
difference in the code.
However, the situation is more complex than that. On 32bit
On Wed, May 08, 2013 at 11:43:22AM +0200, Kevin Wolf wrote:
The device is supposed to reset the Bus Master IDE Active bit in the
status register when 0 is written to the Start/Stop Bus Master bit in
the command register.
In the common cases this happens automatically because bdrv_drain_all()
From: Fam Zheng f...@redhat.com
Zero sized disk is not supported by qemu vmdk driver, exclude vmdk from
the test script.
As tested on vmware-vdiskmanager and vmware workstation, zero sized disk
is not supported by vmware, either.
Signed-off-by: Fam Zheng f...@redhat.com
Reviewed-by: Jeff Cody
This tests the behaviour of the DMA engine when the given PRDT contains
physical region descriptors for either more or less bytes than the
IDE request is for.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/ide-test.c | 54 ++
1 file
From: Fam Zheng f...@redhat.com
043 tests recursive backing file by changing backing file. VMDK has not
implemented this yet, and qcow1 probably never will.
Signed-off-by: Fam Zheng f...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/qemu-iotests/043 | 2 +-
1 file changed, 1
The following changes since commit 15d23fb96656b1ae31bf4305b2108230c29298c6:
Update version for qemu-1.5.0-rc0 (2013-05-07 06:50:19 -0500)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-anthony
for you to fetch changes up to
This adds a simple IDE test case and starts by verifying that IDENTIFY
can be successfully used and return the correct serial number, version
and the WCE flag is set for cache=writeback.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/Makefile | 2 +
tests/ide-test.c | 165
From: Fam Zheng f...@redhat.com
017 and 018 use /bin/mv to move base img from t.IMGFMG to t.IMGFMT.base
after filling data, this is not enough for vmdk, when t.IMGFMT is only a
description text file who points to t-{flat,s001,f001,...}.IMGFMT as
data extent, so testing such subformats alway fails
The device is supposed to reset the Bus Master IDE Active bit in the
status register when 0 is written to the Start/Stop Bus Master bit in
the command register.
In the common cases this happens automatically because bdrv_drain_all()
flushes the requests, but with a large PRDT it could remain set.
On Mon, May 06, 2013 at 04:02:58PM +0200, Kevin Wolf wrote:
An IDE bus provided by AHCI can only take a single IDE drive. If you add
a drive as slave, qemu used to accept the command line but the device
wouldn't be actually usable. Catch the situation instead and error out.
Signed-off-by:
This tests that single sectors can be successfully written and correctly
read back.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/ide-test.c | 221 +++
1 file changed, 221 insertions(+)
diff --git a/tests/ide-test.c b/tests/ide-test.c
An IDE bus provided by AHCI can only take a single IDE drive. If you add
a drive as slave, qemu used to accept the command line but the device
wouldn't be actually usable. Catch the situation instead and error out.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/ide/ahci.c | 2 +-
Aurelien Jarno aurel...@aurel32.net writes:
That said this does implement neither the specification nor the silicon
behaviour. This is fine for 1.5 as we are in freeze period, but this
should be fixed for the 1.6 release.
I talked to IBM now. Reserved fields should be ignored by
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/libqos/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/pci.c b/tests/libqos/pci.c
index 95e287b..7e0907b 100644
--- a/tests/libqos/pci.c
+++ b/tests/libqos/pci.c
@@ -71,7 +71,7 @@ void
Signed-off-by: Kevin Wolf kw...@redhat.com
---
po/de_DE.po | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/po/de_DE.po b/po/de_DE.po
index 92c5df5..e35aaf4 100644
--- a/po/de_DE.po
+++ b/po/de_DE.po
@@ -18,11 +18,11 @@ msgstr
#: ../ui/gtk.c:213
msgid - Press
On Wed, May 08, 2013 at 04:48:22PM +0200, Torbjorn Granlund wrote:
Aurelien Jarno aurel...@aurel32.net writes:
That said this does implement neither the specification nor the silicon
behaviour. This is fine for 1.5 as we are in freeze period, but this
should be fixed for the 1.6
In Windows guests this may make a difference.
Since the original patch (commit c689b4f1) sought to be pedantic and to
consider theoretical corner cases of portability, we should fix it up
where it failed to come through in that pursuit.
Suggested-by: Eric Blake ebl...@redhat.com
Reviewed-by:
We shouldn't allow guest filesystem pollution on error paths.
Suggested-by: Eric Blake ebl...@redhat.com
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
qga/commands-posix.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
I should have paid more attention to portability and error path cleanup
in the CVE-2013-2007 fix.
(We continue to assume, like the rest of qemu code, that
qemu_set_cloexec() never fails internally. This should be a reasonable
assumption when the input fd is valid.)
Laszlo Ersek (2):
qga:
Quoting Maxim Loparev (laplander...@gmail.com):
The issue mostly gone after cold reboot via suspend to disk. I managed to
reproduce it only once after reboot and it grubs CPU for only minute or two
while i checking it and than returned to normal CPU usage. I've checked both
distribution and
Paolo Bonzini pbonz...@redhat.com writes:
I think that would be faster on 32-bit hosts, truncs are cheap.
And slower perhaps on 64-bit hosts, at least for operations where
additional explicit trunctation will be needed (such as before
comparisions and after right shifts).
There could be
Aurelien Jarno aurel...@aurel32.net writes:
As it seems you have good contact with IBM, could you please ask them
to fix their manuals?
What flaw have your found?
At least Freescale CPUs match what IBM documentation says.
Which ones? Freescale 7447 and Freescale e500 disagree. (Or at
Il 08/05/2013 14:39, Kevin Wolf ha scritto:
Am 29.04.2013 um 09:42 hat Stefan Hajnoczi geschrieben:
From: Dietmar Maurer diet...@proxmox.com
backup_start() creates a block job that copies a point-in-time snapshot
of a block device to a target block device.
We call backup_do_cow() for each
Il 08/05/2013 08:20, liu ping fan ha scritto:
On Mon, May 6, 2013 at 10:25 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Hi,
this is an alternative approach to refactoring of dataplane's HostMem
code. Here, I take Ping Fan's idea of RCU-style updating of the
region list and apply it to the
A few notes for anyone trying this...
* I recommend the q35 machine type and using the default config
file found in the docs directory. This means your command line
should include:
-M q35 -nodefconfig -readconfig /path/to/qemu.git/docs/q35-chipset.cfg
*
Il 08/05/2013 17:44, Torbjorn Granlund ha scritto:
Paolo Bonzini pbonz...@redhat.com writes:
I think that would be faster on 32-bit hosts, truncs are cheap.
And slower perhaps on 64-bit hosts, at least for operations where
additional explicit trunctation will be needed (such as before
On Wed, May 08, 2013 at 05:54:27PM +0200, Torbjorn Granlund wrote:
Aurelien Jarno aurel...@aurel32.net writes:
As it seems you have good contact with IBM, could you please ask them
to fix their manuals?
What flaw have your found?
Don't people read what I write? From one of my
On Wed, May 08, 2013 at 04:09:04PM +0200, Petar Jovanovic wrote:
From: Petar Jovanovic petar.jovano...@imgtec.com
The emulator needs to check in hflags if DSP unit has been turned off before
it generates code for MUL_PH, MUL_S_PH, MULQ_S_W, and MULQ_RS_W.
Signed-off-by: Petar Jovanovic
Il 08/05/2013 11:43, Kevin Wolf ha scritto:
This tests that single sectors can be successfully written and correctly
read back.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/ide-test.c | 221
+++
1 file changed, 221
On 05/07/2013 07:50 PM, Paolo Bonzini wrote:
Il 07/05/2013 09:20, Li Zhang ha scritto:
Hi all,
Hi,
When we use the latest version of QEMU to build ovirt,
we get this error reported from libvirt.
What QEMU commit is this?
b3e6d591b05538056d665572f3e3bbfb3cbb70e7
This commit is from
Aurelien Jarno aurel...@aurel32.net writes:
Don't people read what I write? From one of my previous email:
I do...and even scrutinise it for grammar errors. ;-)
Quoting the IBM PowerPC Microprocessor Family: The Programming
On 05/08/2013 09:31 AM, Laszlo Ersek wrote:
We shouldn't allow guest filesystem pollution on error paths.
Suggested-by: Eric Blake ebl...@redhat.com
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
qga/commands-posix.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
On 05/08/2013 02:50 AM, qiaonuohan wrote:
Thanks for your suggestion. I will fix it like:
{ 'enum': 'DumpCompressionFormat',
'data': [ 'zlib', 'lzo', 'snappy' ] }
For zlib is treated as the default compression format, and
'uncompressed' won't be an option.
No, I was serious that you
[assuming you mis-typed your cc:, and that you meant kwolf instead of
kwol at redhat]
On 05/08/2013 02:45 AM, Dong Xu Wang wrote:
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
---
include/qemu/option.h | 32 --
util/qemu-option.c| 285 -
On Tue, May 07, 2013 at 07:01:13PM -0400, Kevin O'Connor wrote:
On Tue, May 07, 2013 at 09:00:48PM +0300, Michael S. Tsirkin wrote:
On Thu, Apr 25, 2013 at 12:02:20PM +0300, Michael S. Tsirkin wrote:
Untested yet, but I thought I'd share the
BIOS bits so we can agree on direction.
Update:
From our testing this bug affects KVM Hypervisors on Intel processors
that have the EPT feature enabled with Kernels 3.0 and greater. A list
of Intel EPT supported CPUs here
(http://ark.intel.com/Products/VirtualizationTechnology).
When using a KVM Hypervisor Host with Linux kernel 3.0
When running an L=1 cmp instruction on a 64bit PPC CPU with SF off, it
still behaves identical to what it does when SF is on. Remove the implicit
difference in the code.
Also, on most 32bit CPUs we should always treat the compare as 32bit
compare, as the CPU will ignore the L bit. This is not
Hi Blue / Aurelien,
This is my current patch queue for ppc with fixes that need to go into 1.5.
Please pull.
Alex
The following changes since commit c0f5f9ce86ddca0a7d7ca60012059a5a18aa9c07:
Petar Jovanovic (1):
target-mips: fix incorrect behaviour for INSV
are available in the git
The implementation for rldcl tried to always fetch its
parameters from the opcode, even though the opcode was
already passed in in decoded and different forms.
Use the parameters instead, fixing rldcl.
Reported-by: Torbjorn Granlund t...@gmplib.org
Reviewed-by: Aurelien Jarno
When running an L=1 cmp instruction on a 64bit PPC CPU with SF off, it
still behaves identical to what it does when SF is on. Remove the implicit
difference in the code.
Also, on most 32bit CPUs we should always treat the compare as 32bit
compare, as the CPU will ignore the L bit. This is not
On Tue, May 07, 2013 at 03:49:58PM +0300, Michael S. Tsirkin wrote:
mask notifiers are never called without msix,
so devices with backend masking like vhost don't work.
Call mask notifiers explicitly at
startup/cleanup to make it work.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1100843
Title:
Live Migration Causes Performance Issues
Status in QEMU:
On Wed, May 08, 2013 at 08:21:56PM +0200, Alexander Graf wrote:
When running an L=1 cmp instruction on a 64bit PPC CPU with SF off, it
still behaves identical to what it does when SF is on. Remove the implicit
difference in the code.
Also, on most 32bit CPUs we should always treat the
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1100843
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
I don't know if this will help, but I had a similar problem.
When creating a snapshot image of an XP machine, all works just fine
when loading it. As time passes on the host the loadvm start to become
very slow.
To reproduce:
1. Create a snapshot image (savevm)
2. leave QEMU
3. move the *HOST*
Paolo Bonzini pbonz...@redhat.com writes:
Il 07/05/2013 10:26, Laszlo Ersek ha scritto:
I suspected that something like this was in the background, but what I
didn't understand was: why single out the public domain, as the GPL
itself is in the exact same bucket, generally speaking.
I think
On Wed, May 08, 2013 at 08:24:46PM +0200, Alexander Graf wrote:
Hi Blue / Aurelien,
This is my current patch queue for ppc with fixes that need to go into 1.5.
Please pull.
Alex
The following changes since commit c0f5f9ce86ddca0a7d7ca60012059a5a18aa9c07:
Petar Jovanovic (1):
When setcond2 is rewritten into setcond, the state of the destination
temp should be reset, so that a copy of the previous value is not
used instead of the result.
Reported-by: Michael Tokarev m...@tls.msk.ru
Cc: Richard Henderson r...@twiddle.net
Signed-off-by: Aurelien Jarno
On Wed, May 08, 2013 at 10:42:42PM +0200, Aurelien Jarno wrote:
When setcond2 is rewritten into setcond, the state of the destination
temp should be reset, so that a copy of the previous value is not
used instead of the result.
Reported-by: Michael Tokarev m...@tls.msk.ru
Cc: Richard
On Wed, May 8, 2013 at 12:57 AM, Aurelien Jarno aurel...@aurel32.net wrote:
On Tue, May 07, 2013 at 11:29:20PM +0200, Artyom Tarasenko wrote:
On Tue, May 7, 2013 at 1:38 PM, Torbjorn Granlund t...@gmplib.org wrote:
The 2nd table of http://gmplib.org/devel/testsystems.html shows all
emulated
Hi,
On behalf of the QEMU Team, I'd like to announce the availability of the
second release candidate for the QEMU 1.5 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-1.5.0-rc1.tar.bz2
You can help
git://github.com/jljusten/qemu.git kvm-flash-v5
Utilize KVM_CAP_READONLY_MEM to support PC system flash emulation
with KVM.
v5:
* Remove patch to pflash_cfi01 which enabled readonly mode
* Adjust kvm code to use KVM READONLY support for ranges that
either have the readonly flag set, or for
When pc-sysfw.rom_only == 0, flash memory will be
usable with kvm. In order to enable flash memory mode,
a pflash device must be created. (For example, by
using the -pflash command line parameter.)
Usage of a flash memory device with kvm requires
KVM_CAP_READONLY_MEM, and kvm will abort if
a
Signed-off-by: Jordan Justen jordan.l.jus...@intel.com
---
include/sysemu/kvm.h | 10 ++
kvm-all.c|6 ++
kvm-stub.c |1 +
3 files changed, 17 insertions(+)
diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
index 9735c1d..13c4b2e 100644
---
Now KVM can support a flash memory. This feature depends on
KVM_CAP_READONLY_MEM, which was introduced in Linux 3.7.
Flash memory will only be enabled if a pflash device is
created. (For example, by using the -pflash command line
parameter.)
Signed-off-by: Jordan Justen jordan.l.jus...@intel.com
The isapc machine with seabios currently requires the BIOS region
to be read/write memory rather than read-only memory.
KVM currently cannot support the BIOS as a ROM region, but qemu
in non-KVM mode can. Based on this, isapc machine currently only
works with KVM.
To work-around this isapc
For readonly memory regions and rom devices that are readable,
we make use of the KVM_MEM_READONLY. A slot that uses
KVM_MEM_READONLY can be read from and code can execute from the
region, but writes will exit to qemu.
For rom devices that are not readable, we force the slot to be
removed so
On Wed, May 08, 2013 at 03:35:46PM +0300, Michael S. Tsirkin wrote:
On Wed, May 08, 2013 at 02:35:44PM +0300, Gleb Natapov wrote:
On Wed, May 08, 2013 at 02:07:24PM +0300, Michael S. Tsirkin wrote:
On Wed, May 08, 2013 at 01:59:12PM +0300, Gleb Natapov wrote:
Where this notion that
These patches apply on top of qemu.git master, and can also be obtained from:
git://github.com/mdroth/qemu.git qapi-native-lists
Sending this now since a number of series have popped up in the past that
wanted this, and Amos has some pending patches (query-mac-tables) that rely
on this as well.
Currently we assume non-list types when generating visitor routines for
union types. This is broken, since values like ['Type'] need to mapped
to 'TypeList'.
We already have a type_name() function to handle this that we use for
generating struct visitors, so use that here as well.
Signed-off-by:
Teach type generators about native types so they can generate the
appropriate linked list types.
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
scripts/qapi-types.py | 44 +---
scripts/qapi.py | 21 +
2 files
Also, fix a dependency issue with libqemuutil: qemu-sockets.c needs
qapi-types.c/qapi-visit.c
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
Makefile |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 7dc0204..9695c9d 100644
---
qmp_output_get_qobject() increments the qobject's reference count. Since
we currently pass this straight into qobject_to_json() so we can feed
the data into a QMP input visitor, we never actually free the underlying
qobject when qmp_output_visitor_cleanup() is called. This causes leaks
on all of
Teach visitor generators about native types so they can generate the
appropriate visitor routines.
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
scripts/qapi-visit.py | 34 +-
1 file changed, 29 insertions(+), 5 deletions(-)
diff --git
This exercises schema-generated visitors for native list types and does
some sanity checking on validity of serialized data.
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
qapi-schema-test.json |8 ++
tests/test-qmp-output-visitor.c | 172
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
tests/test-visitor-serialization.c | 247 +---
1 file changed, 229 insertions(+), 18 deletions(-)
diff --git a/tests/test-visitor-serialization.c
b/tests/test-visitor-serialization.c
index
This exercises schema-generated visitors for native list types and does
some sanity checking on validity of deserialized data.
Signed-off-by: Michael Roth mdr...@linux.vnet.ibm.com
---
tests/test-qmp-input-visitor.c | 181
1 file changed, 181
The current implementation checked for supported filesystems at mount
time, but actual support depends on the path. Don't error out when
finding unversioned paths.
This fix allows booting a linux kernel with the same / filesystem as the
host; otherwise the boot fails when mounting devtmpfs.
The current implementation checked for supported filesystems at mount
time, but actual support depends on the path. Don't error out when
finding unversioned paths.
This fix allows booting a linux kernel with the same / filesystem as the
host; otherwise the boot fails when mounting devtmpfs.
在 2013-05-08三的 10:48 -0300，Eduardo Habkost写道：
On Wed, May 08, 2013 at 01:43:22PM +0800, li guang wrote:
ping ...
I guess this didn't get any attention because we were already past soft
freeze, and the focus was to get important features/fixes in shape
before hard freeze.
OK, thanks for
On 05/08/2013 04:45:45 AM, Torbjorn Granlund wrote:
Paolo Bonzini pbonz...@redhat.com writes:
I guess that's the register windows. There's only so much you can
do to
optimize them, and heavily recursive workloads (like Perl, or the
RTL
half of GCC) pay a hefty price.
Two qemu
Currently pci_find_domain() performs two functions - it locates the PCI
root bus above the given bus, then looks up that root bus's domain number.
This patch adds a helper function to perform the first task, finding the
root bus for a given PCI device. This is then used in pci_find_domain().
This
pci_find_domain() is used in a number of places where we want an id for a
whole PCI domain (i.e. the subtree under a PCI root bus). The trouble is
that many platforms may support multiple independent host bridges with no
hardware supplied notion of domain number.
This patch, therefore, replaces
pci-hotplug.c and the CONFIG_PCI_HOTPLUG variable which controls its
compilation are misnamed. They're not about PCI hotplug in general, but
rather about the pci_add/pci_del interface which are now deprecated in
favour of the more general device_add/device_del interface. This patch
therefore
There are now no users of the domain field of PCIHostBus, so remove it
from the structure, and as a parameter from the pci_host_bus_register()
function which sets it.
Signed-off-by: David Gibson da...@gibson.dropbear.id.au
---
hw/pci/pci.c |6 ++
1 file changed, 2 insertions(+), 4
The host_buses list is an odd structure - a list of pointers to PCI root
buses existing in parallel to the normal qdev tree structure. This patch
removes it, instead putting the link pointers into the PCIHostState
structure, which have a 1:1 relationship to PCIHostBus structures anyway.
pci_find_root_bus() takes a domain parameter. Currently PCI root buses
with domain other than 0 can't be created, so this is more or less a long
winded way of retrieving the main PCI root bus. Numbered domains don't
actually properly cover the (non x86) possibilities for multiple PCI root
buses,
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Hosts threads which handle vring should have high MemoryListener priority
than kvm. For currently code, take the following scenario:
kvm_region_add() run earlier before vhost_region_add(), then in guest,
vring's desc[i] can refer to addressX in the
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
It will make the priority prominent, when new listener added.
All the priority's value are kept unchanged, except for vhost
and hostmem.(Changes introduced by prev patch)
Signed-off-by: Liu Ping Fan pingf...@linux.vnet.ibm.com
---
exec.c
Hi!
On 05/09/2013 01:53 AM, fred.kon...@greensocs.com wrote:
On 05/07/2013 07:50 PM, Paolo Bonzini wrote:
Il 07/05/2013 09:20, Li Zhang ha scritto:
Hi all,
Hi,
When we use the latest version of QEMU to build ovirt,
we get this error reported from libvirt.
What QEMU commit is this?
On Tue, May 7, 2013 at 10:16 PM, Paolo Bonzini pbonz...@redhat.com wrote:
memory_region_find() is similar to registering a MemoryListener and
But losing the priority of MemoryListener. Had better document to
warn this, so the user will decide whether it is safe to use the
interfaces based on
Currently pci_get_primary_bus() searches the list of root buses for one
with domain 0. But since host buses are always registered with domain 0,
this just amounts to finding the only PCI host bus.
This simplifies the implementation by defining the primary PCI bus to
be the first one registered,
pci_read_devaddr() is only used by the legacy functions for the old PCI
hotplug interface in pci-hotplug-old.c. So we move the function there,
and make it static.
Signed-off-by: David Gibson da...@gibson.dropbear.id.au
---
hw/pci/pci-hotplug-old.c | 14 ++
hw/pci/pci.c
The current PCI subsystem has kind of half-hearted support for
multiple independent root buses - aka PCI domains - in the form of the
PCIHostBus structure and its domain field. However, it doesn't quite
work because pci_host_bus_register() is always called with a domain of
0.
Worse, though, the
On Wed, May 8, 2013 at 11:44 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 08/05/2013 08:20, liu ping fan ha scritto:
On Mon, May 6, 2013 at 10:25 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Hi,
this is an alternative approach to refactoring of dataplane's HostMem
code. Here, I take Ping
On 2013/5/9 1:59, Eric Blake wrote:
[assuming you mis-typed your cc:, and that you meant kwolf instead of
kwol at redhat]
On 05/08/2013 02:45 AM, Dong Xu Wang wrote:
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
---
include/qemu/option.h | 32 --
util/qemu-option.c| 285
On Wed, May 8, 2013 at 12:08 AM, Paolo Bonzini pbonz...@redhat.com wrote:
- Messaggio originale -
Da: Peter Maydell peter.mayd...@linaro.org
A: Paolo Bonzini pbonz...@redhat.com
Cc: qemu-devel@nongnu.org, a...@ozlabs.ru, jan kiszka
jan.kis...@siemens.com, qemul...@gmail.com,
101 - 200 of 206 matches
Mail list logo
