From: Peter Crosthwaite peter.crosthwa...@xilinx.com
This message was printing out the data in decimal only, which is not
very friendly to the debugging developer. Add hex variant in
parenthesis to make it consistent with other similar messages in this
module.
Signed-off-by: Peter Crosthwaite
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
The end of transfer check was occurring and potentially returning before
the interrupt flag was checked. This means the interrupt will be missed
if it occurs on the last packet. Fix by checking for the interrupt
before checking for the end of
In the case of physical hard disk's speed which processing IO (when grouping
RAID) is very slow, I encountered a problem.
I dd big file in SUSE virtual machine, the command is
linux:/ # dd if=/dev/zero of=./info bs=1M count=5000;sync
but finally I get those message:
linux:~ # dmesg
[
On Mon, May 20, 2013 at 09:23:43AM +0200, Paolo Bonzini wrote:
Il 20/05/2013 08:24, Stefan Hajnoczi ha scritto:
You only need to fdatasync() before every guest flush, no?
No, you need to set the dirty bit before issuing the write on the
host. Otherwise the image data may be modified
On Tue, May 21, 2013 at 12:46:09PM +0800, Amos Kong wrote:
On Fri, May 17, 2013 at 09:39:31AM +0200, Stefan Hajnoczi wrote:
On Thu, May 16, 2013 at 07:07:25PM +0800, Amos Kong wrote:
Hi Stefan,
@@ -961,6 +961,44 @@ void print_net_client(Monitor *mon, NetClientState
*nc)
On Tue, May 21, 2013 at 09:54:15AM +0800, Fam Zheng wrote:
On Mon, 05/20 09:49, Richard W.M. Jones wrote:
On Mon, May 20, 2013 at 09:41:06AM +0100, Richard W.M. Jones wrote:
On Mon, May 20, 2013 at 03:03:34PM +0800, Fam Zheng wrote:
CURL library API has changed, the current curl driver
On Tue, May 21, 2013 at 11:25:01AM +0800, Wenchao Xia wrote:
于 2013-5-17 17:14, Stefan Hajnoczi 写道:
On Fri, May 17, 2013 at 02:58:57PM +0800, Wenchao Xia wrote:
于 2013-5-16 15:47, Stefan Hajnoczi 写道:
On Thu, May 16, 2013 at 02:16:20PM +0800, Wenchao Xia wrote:
After checking the code, I
Public bug reported:
I use Qemu (Git 1239b472bb0dba8060f1af29d40dafbc1b2860d4) to test a SMP
application on ARM. I use the following command line:
qemu-system-arm -S -s -net none -nographic -M realview-pbx-a9 -kernel
app.exe -m 256M -no-reboot -smp 2 -icount 8
The application crashes because
On Mon, May 20, 2013 at 11:04:29PM +0530, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
With mapped security models like mapped-xattr and mapped-file, we save the
symlink target as file contents. Now if we ever expose a normal directory
with mapped security
On Fri, May 17, 2013 at 04:08:36PM +0100, Peter Maydell wrote:
On 17 May 2013 14:51, Stefan Hajnoczi stefa...@redhat.com wrote:
There is ongoing work to enable multiple event loop threads. This will
allow
QEMU itself to take advantage of SMP and reduce Big QEMU Lock (BQL)
contention.
Oops, correct libvirt mailing list address. :)
Thanks.
On 2013年05月21日 16:19, Li Zhang wrote:
Hi all,
Sorry to bring this problem up again.
We encounter this problem in openstack which always use
default machine type. Currently, QEMU sets mac99 as default
setting for ppc64 but it doesn't
Hi all,
Sorry to bring this problem up again.
We encounter this problem in openstack which always use
default machine type. Currently, QEMU sets mac99 as default
setting for ppc64 but it doesn't work on our platform at all.
I tried to fix this in libvirt which it is not acceptable because
Il 21/05/2013 09:31, Stefan Hajnoczi ha scritto:
On Mon, May 20, 2013 at 09:23:43AM +0200, Paolo Bonzini wrote:
Il 20/05/2013 08:24, Stefan Hajnoczi ha scritto:
You only need to fdatasync() before every guest flush, no?
No, you need to set the dirty bit before issuing the write on the
host.
Can you attach or provide a link to your app.exe test case? Otherwise
this is going to be harder to track down and test. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182344
Title:
ARM:
On 21 May 2013 09:19, Li Zhang zhlci...@gmail.com wrote:
We encounter this problem in openstack which always use
default machine type. Currently, QEMU sets mac99 as default
setting for ppc64 but it doesn't work on our platform at all.
I tried to fix this in libvirt which it is not acceptable
Il 21/05/2013 10:33, Amos Kong ha scritto:
On Thu, May 16, 2013 at 05:20:37PM +0200, Paolo Bonzini wrote:
Il 16/05/2013 17:17, Peter Maydell ha scritto:
On 16 May 2013 16:09, Paolo Bonzini pbonz...@redhat.com wrote:
... In XWindows, you get a KeyRelease for every KeyPress Event. In X,
it
On Tue, May 21, 2013 at 09:31:26AM +0100, Peter Maydell wrote:
On 21 May 2013 09:19, Li Zhang zhlci...@gmail.com wrote:
We encounter this problem in openstack which always use
default machine type. Currently, QEMU sets mac99 as default
setting for ppc64 but it doesn't work on our platform
On Thu, May 16, 2013 at 05:20:37PM +0200, Paolo Bonzini wrote:
Il 16/05/2013 17:17, Peter Maydell ha scritto:
On 16 May 2013 16:09, Paolo Bonzini pbonz...@redhat.com wrote:
... In XWindows, you get a KeyRelease for every KeyPress Event. In X,
it looks something like this:
On Tue, May 21, 2013 at 01:04:55PM +0800, Amos Kong wrote:
On Thu, May 16, 2013 at 03:17:45PM +0300, Michael S. Tsirkin wrote:
On Thu, May 16, 2013 at 07:07:24PM +0800, Amos Kong wrote:
Introduce this new QMP event to notify management after guest changes
mac-table configuration.
+
On 21 May 2013 09:39, Daniel P. Berrange berra...@redhat.com wrote:
Libvirt has always had support for specifying what machine type to use.
This discussion is simply about what machine type to default to, if the
user hasn't explicitly asked for one.
QEMU has the notion of a default machine
On 2013年05月21日 16:31, Peter Maydell wrote:
On 21 May 2013 09:19, Li Zhang zhlci...@gmail.com wrote:
We encounter this problem in openstack which always use
default machine type. Currently, QEMU sets mac99 as default
setting for ppc64 but it doesn't work on our platform at all.
I tried to fix
On Mon, May 20, 2013 at 02:44:25PM -0600, Bjorn Helgaas wrote:
On Mon, May 20, 2013 at 12:32 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, May 20, 2013 at 11:09:56AM -0600, Bjorn Helgaas wrote:
Indicate ASPM L0s and L1 support in Link Capabilities and make the ASPM
bits in Link
On 2013年05月21日 16:45, Peter Maydell wrote:
On 21 May 2013 09:39, Daniel P. Berrange berra...@redhat.com wrote:
Libvirt has always had support for specifying what machine type to use.
This discussion is simply about what machine type to default to, if the
user hasn't explicitly asked for one.
On Tue, May 21, 2013 at 10:38:00AM +0200, Paolo Bonzini wrote:
Il 21/05/2013 10:33, Amos Kong ha scritto:
On Thu, May 16, 2013 at 05:20:37PM +0200, Paolo Bonzini wrote:
Il 16/05/2013 17:17, Peter Maydell ha scritto:
On 16 May 2013 16:09, Paolo Bonzini pbonz...@redhat.com wrote:
... In
** Attachment added: ELF file of the application.
https://bugs.launchpad.net/qemu/+bug/1182344/+attachment/3682743/+files/app.exe
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182344
Title:
On 21 May 2013 10:02, Li Zhang zhlci...@gmail.com wrote:
On 2013年05月21日 16:45, Peter Maydell wrote:
On 21 May 2013 09:39, Daniel P. Berrange berra...@redhat.com wrote:
Libvirt has always had support for specifying what machine type to use.
OK, that makes sense. So is the problem here just
On Tue, May 21, 2013 at 05:02:51PM +0800, Li Zhang wrote:
On 2013年05月21日 16:45, Peter Maydell wrote:
On 21 May 2013 09:39, Daniel P. Berrange berra...@redhat.com wrote:
Libvirt has always had support for specifying what machine type to use.
This discussion is simply about what machine type to
On 21 May 2013 07:50, peter.crosthwa...@xilinx.com wrote:
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
the SD command ACMD41 can be used in a read only mode to query device
state without doing the SD card initialisation. This is valid even
which the device is already initialised. Fix
On Tue, May 21, 2013 at 05:04:30PM +0800, Amos Kong wrote:
On Tue, May 21, 2013 at 10:38:00AM +0200, Paolo Bonzini wrote:
Please correct me if something is wrong, thanks.
When we use VNC/SPICE/SDL, vm Window will captured the key events,
then qemu process the events and transfer to
On 21 May 2013 07:52, peter.crosthwa...@xilinx.com wrote:
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
This message was printing out the data in decimal only, which is not
very friendly to the debugging developer. Add hex variant in
parenthesis to make it consistent with other
Il 21/05/2013 11:51, Amos Kong ha scritto:
On Tue, May 21, 2013 at 05:04:30PM +0800, Amos Kong wrote:
On Tue, May 21, 2013 at 10:38:00AM +0200, Paolo Bonzini wrote:
Please correct me if something is wrong, thanks.
When we use VNC/SPICE/SDL, vm Window will captured the key events,
then qemu
On Tue, May 21, 2013 at 07:55:27PM +1000, Paul Mackerras wrote:
On Tue, May 21, 2013 at 09:39:53AM +0100, Daniel P. Berrange wrote:
On Tue, May 21, 2013 at 09:31:26AM +0100, Peter Maydell wrote:
On 21 May 2013 09:19, Li Zhang zhlci...@gmail.com wrote:
We encounter this problem in
On 21 May 2013 11:01, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, May 21, 2013 at 07:55:27PM +1000, Paul Mackerras wrote:
I think libvirt needs some more sensible way to ask qemu what its
capabilities are. Currently it has no way to ask qemu what machines
can you emulate with kvm
On 05/20/2013 11:15 PM, Paolo Bonzini wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 20/05/2013 17:05, Eric Blake ha scritto:
On 05/20/2013 04:59 AM, Paolo Bonzini wrote:
Il 20/05/2013 12:43, Paolo Bonzini ha scritto:
Il 20/05/2013 08:51, Lei Li ha scritto:
Now we have ringbuf char
This patch sets the filename when the new qapi backend
init from opts.
The previous patch and discussions as link below:
http://patchwork.ozlabs.org/patch/243896/
If anyone who have better idea to fix this please let
me know your suggestions.
Signed-off-by: Lei Li li...@linux.vnet.ibm.com
---
On Tue, May 21, 2013 at 10:30:22AM +0200, Paolo Bonzini wrote:
Il 21/05/2013 09:31, Stefan Hajnoczi ha scritto:
On Mon, May 20, 2013 at 09:23:43AM +0200, Paolo Bonzini wrote:
Il 20/05/2013 08:24, Stefan Hajnoczi ha scritto:
You only need to fdatasync() before every guest flush, no?
No,
Il 21/05/2013 12:34, Stefan Hajnoczi ha scritto:
On Tue, May 21, 2013 at 10:30:22AM +0200, Paolo Bonzini wrote:
Il 21/05/2013 09:31, Stefan Hajnoczi ha scritto:
On Mon, May 20, 2013 at 09:23:43AM +0200, Paolo Bonzini wrote:
Il 20/05/2013 08:24, Stefan Hajnoczi ha scritto:
You only need to
This series tries to fix the consistency of char devices
ringbuf and a regression of chardev filename.
Changes since v1:
- Rename the struct related to new qapi ringbuf to memory, and
fix the wrong description in qemu-option from Paolo.
Lei Li (2):
chardev: Make the name of memory device
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend called it 'ringbuf'. It should keep
consistent. This patch named it all to 'memory'.
This is part 1 of the memory API updates for 1.6. (Part 2 is the
introduction of get/set_owner, part 3 is the introduction of the
RCU-style flatview).
Compared to the first submissions, there are a few extra cleanup
patches, and address_space_rw/read/write grew a return value so
that the
See how we call memory_region_section_addr two lines below to
convert a physical address to a base address in the region.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/exec.c b/exec.c
index aec65c5..197625c 100644
---
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c| 8
hw/pci/pci.c | 2 --
hw/scsi/megasas.c | 1 -
include/exec/cpu-common.h | 1 -
trace-events | 3 ---
5 files changed, 15 deletions(-)
diff --git a/exec.c b/exec.c
index
While sized to 15 bits in PhysPageEntry, the ptr field is ORed into the
iotlb entries together with a page-aligned pointer. The ptr field must
not overflow into this page-aligned value, assert that it is smaller than
the page size.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 2
It is not used anywhere.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c| 27 ---
include/exec/cpu-common.h | 1 -
include/exec/poison.h | 1 -
3 files changed, 29 deletions(-)
diff --git a/exec.c b/exec.c
index fa5f9c3..1355661
From: Jan Kiszka jan.kis...@siemens.com
Readable is a very unfortunate name for this flag because even a
rom_device region will always be readable from the guest POV. What
differs is the mapping, just like the comments had to explain already.
Also, readable could currently be understood as being
It is a private interface between exec.c and memory.c.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
include/exec/cpu-common.h | 2 --
include/exec/memory-internal.h | 1 +
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/exec/cpu-common.h
From: Avi Kivity avi.kiv...@gmail.com
A couple of fields were left uninitialized. This was not observed earlier
because all address spaces were statically allocated. Also free allocation
for those fields.
Signed-off-by: Avi Kivity avi.kiv...@gmail.com
Signed-off-by: Paolo Bonzini
From: Jan Kiszka jan.kis...@siemens.com
Improves readability.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
translate-all.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/translate-all.c b/translate-all.c
index da93608..0d84b0d 100644
--- a/translate-all.c
+++
The old-style IOMMU lets you check whether an access is valid in a
given DMAContext. There is no equivalent for AddressSpace in the
memory API, implement it with a lookup of the dispatch tree.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
dma-helpers.c | 5 +
exec.c
memory_region_find() is similar to registering a MemoryListener and
checking for the MemoryRegionSections that come from a particular
region. There is no reason for this to be limited to a root memory
region.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
include/exec/memory.h | 13
Remove the goto.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/exec.c b/exec.c
index 8f1b507..82da067 100644
--- a/exec.c
+++ b/exec.c
@@ -187,19 +187,15 @@ MemoryRegionSection
Suggested-by: Peter Maydell peter.mayd...@linaro.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
arch_init.c | 2 +-
include/exec/memory.h | 7 +++
memory.c | 3 +--
3 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c| 23 ++-
include/exec/memory.h | 12 +---
2 files changed, 19 insertions(+), 16 deletions(-)
diff --git a/exec.c b/exec.c
index e5ee8ff..4cc5ecb 100644
--- a/exec.c
+++ b/exec.c
@@ -1901,7
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
memory.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/memory.c b/memory.c
index 013464b..5431463 100644
--- a/memory.c
+++ b/memory.c
@@ -768,10 +768,6 @@ static void
memory_region_destructor_ram_from_ptr(MemoryRegion *mr)
From: Jan Kiszka jan.kis...@siemens.com
This introduces a wrapper for phys_page_find (before we complicate
address_space_translate with IOMMU translation). This function will
also encapsulate locking and reference counting when we introduce
BQL-free dispatching.
Signed-off-by: Jan Kiszka
The TCE table is currently returned as a DMAContext, and non-type-safe
APIs are called later passing back the DMAContext. Since we want to move
away from DMAContext, use an opaque type instead, and add an accessor
to retrieve the DMAContext from it.
Acked-by: David Gibson
From: Avi Kivity avi.kiv...@gmail.com
vfio doesn't support guest iommus yet, indicate it to the user
by gently depositing a core on their disk.
Signed-off-by: Avi Kivity avi.kiv...@gmail.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/misc/vfio.c | 2 ++
1 file changed, 2
The next step is to introduce the translation code that will be used for
IOMMU MemoryRegions, but still do the actual translation in a DMAContext.
Acked-by: David Gibson da...@gibson.dropbear.id.au
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/ppc/spapr_iommu.c | 59
From: Alexey Kardashevskiy a...@ozlabs.ru
The info mtree command in QEMU console prints only memory and I/O
address spaces while there are actually a lot more other AddressSpace
structs created by PCI and VIO devices. Those devices do not normally
have names and therefore not present in info
Even a new address space might have a non-empty FlatView. In order
to initialize it properly, address_space_init should (a) call
memory_region_transaction_commit after the address space is inserted
into the list; (b) force memory_region_transaction_commit to do something.
This bug was latent so
From: Avi Kivity avi.kiv...@gmail.com
Use the new iommu support in the memory core for iommu support. The only
user, spapr, is also converted, but it still provides a DMAContext
interface until the non-PCI bits switch to AddressSpace.
Cc: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Avi
Using phys_page_find to translate an AddressSpace to a MemoryRegionSection
is unwieldy. It requires to pass the page index rather than the address,
and later memory_region_section_addr has to be called. Replace
memory_region_section_addr with a function that does all of it: call
phys_page_find,
The DMAContext is a simple pointer to an AddressSpace that is now always
already available. Make everyone hold the address space directly,
and clean up the DMA API to use the AddressSpace directly.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
dma-helpers.c | 24
The translate function in the DMAContext is now always NULL.
Remove every reference to it.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
dma-helpers.c| 178 +++
exec.c | 3 +-
hw/pci/pci.c | 3 +-
From: Avi Kivity avi.kiv...@gmail.com
Add a new memory region type that translates addresses it is given,
then forwards them to a target address space. This is similar to
an alias, except that the mapping is more flexible than a linear
translation and trucation, and also less efficient since the
True, but that would happen only in case the host crashes. Even for
a QEMU crash the changes would be safe, I think. They would be
written back when the persistent dirty bitmap's mmap() area is
unmapped, during process exit.
I'd err on the side of caution, mark the persistent dirty
From: David Gibson da...@gibson.dropbear.id.au
This patch adds a NotifierList to MemoryRegions which represent IOMMUs
allowing other parts of the code to register interest in mappings or
unmappings from the IOMMU. All IOMMU implementations will need to call
memory_region_notify_iommu() to inform
Fetch the root region from the sPAPRTCETable, and use it to build
an AddressSpace and DMAContext.
Now, everywhere we have a DMAContext we also have access to the
corresponding AddressSpace (either because we create it just before
the DMAContext, or because dma_context_memory's AddressSpace is
Hi,
I am trying to find out the Guest VA to Host PA mapping in QEMU. Can
someone give ideas about the data-structures that are used for storing the
same? From the code, It looks like the CPU_X86 state contains control
registers, and from the cr[3] register, I can get the page table address.
but
Now we can stop using a translating DMAContext, but we do not yet modify
the sPAPRTCETable users to get an AddressSpace; they keep using the table
via a DMAContext.
Acked-by: David Gibson da...@gibson.dropbear.id.au
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/ppc/spapr_iommu.c | 49
Nuohan,
Am 21.05.2013 08:16, schrieb Jesse Larrew:
On 05/20/2013 10:00 PM, Qiao Nuohan wrote:
Function walk_pte needs pte index to calculate virtual address. However, pte
index of PAE paging or IA-32e paging is 9 bit, so the mask should be 0x1ff.
---
target-i386/arch_memory_mapping.c |2
Hi all,
Migrating from:
/opt/qemu-1.4.1/bin/qemu-system-x86_64 -M pc -watchdog i6300esb
-watchdog-action reset [...]
to:
/opt/qemu-1.5.0/bin/qemu-system-x86_64 -M pc-i440fx-1.4 -watchdog
i6300esb -watchdog-action reset [...]
I get:
qemu: warning: error while loading state for instance 0x0
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
See how we call memory_region_section_addr two lines below to
convert a physical address to a base address in the region.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
(I'm
Am 21.05.2013 08:05, schrieb peter.crosthwa...@xilinx.com:
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
object_dymamic_cast_assert used to be tolerant of NULL objects and not
dynamic
assert. Its clear from the implementation that this is the expected
It's
behavior.
The
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
It is a private interface between exec.c and memory.c.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
Hi,
Am 21.05.2013 09:12, schrieb Gonglei (Arei):
In the case of physical hard disk's speed which processing IO (when grouping
RAID) is very slow, I encountered a problem.
I dd big file in SUSE virtual machine, the command is
linux:/ # dd if=/dev/zero of=./info bs=1M count=5000;sync
but
From: Avi Kivity avi.kiv...@gmail.com
The radix tree is statically sized to fit TARGET_PHYS_ADDR_SPACE_BITS.
If a larger memory region is registered, it will overflow.
Fix by limiting any section in the radix tree to the supported size.
This problem was not observed earlier since artificial
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
From: Jan Kiszka jan.kis...@siemens.com
Improves readability.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
for about the third time.
-- PMM
Hi,
Am 21.05.2013 13:33, schrieb Nicholas Thomas:
Migrating from:
/opt/qemu-1.4.1/bin/qemu-system-x86_64 -M pc -watchdog i6300esb
-watchdog-action reset [...]
to:
/opt/qemu-1.5.0/bin/qemu-system-x86_64 -M pc-i440fx-1.4 -watchdog
i6300esb -watchdog-action reset [...]
I get:
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
Suggested-by: Peter Maydell peter.mayd...@linaro.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
From: Avi Kivity avi.kiv...@gmail.com
A couple of fields were left uninitialized. This was not observed earlier
because all address spaces were statically allocated. Also free allocation
for those fields.
Signed-off-by: Avi
With the next patch, the memory API will complain if the
TARGET_PHYS_ADDR_SPACE_BITS gets dangerously close to an
overflow. s390x can handle up to 64 bit of physical address
space from its page tables, but we never use that much. Just
decrease the value.
Cc: Alexander Graf ag...@suse.de
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
From: Avi Kivity avi.kiv...@gmail.com
The radix tree is statically sized to fit TARGET_PHYS_ADDR_SPACE_BITS.
If a larger memory region is registered, it will overflow.
Fix by limiting any section in the radix tree to the
On 21 May 2013 11:57, Paolo Bonzini pbonz...@redhat.com wrote:
Even a new address space might have a non-empty FlatView. In order
to initialize it properly, address_space_init should (a) call
memory_region_transaction_commit after the address space is inserted
into the list; (b) force
peter.crosthwa...@xilinx.com writes:
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
object_dymamic_cast_assert used to be tolerant of NULL objects and not
assert. Its clear from the implementation that this is the expected
behavior.
The preceding check of the cast cache dereferences
Hi, Andreas
-Original Message-
From: Andreas Färber [mailto:afaer...@suse.de]
Sent: Tuesday, May 21, 2013 7:50 PM
To: Gonglei (Arei)
Cc: kw...@redhat.com; qemu-devel@nongnu.org; Wangzhenguo; Luonengjun;
Huangweidong (Hardware); Bo Yang
Subject: Re: [Qemu-devel] IDE disk FLUSH take
Daniel P. Berrange berra...@redhat.com writes:
On Tue, May 21, 2013 at 07:55:27PM +1000, Paul Mackerras wrote:
On Tue, May 21, 2013 at 09:39:53AM +0100, Daniel P. Berrange wrote:
QEMU has the notion of a default machine for each target, and that is
what libvirt uses if the user hasn't
On 05/21/2013 07:32 PM, Andreas Färber wrote:
This patch is missing a Signed-off-by!
Ha! I forgot it.
If you can reply with one, I'd fix up the subject for you (it should
indicate where you are fixing it) and queue it together with my CPU'ish
memory_mapping refactorings, if no one objects.
On 21 May 2013 13:04, Anthony Liguori anth...@codemonkey.ws wrote:
We've talked in the past about having an accelerator specific machine
default. I think this is a perfectly reasonable thing to do and would
solve the problem for ARM and for PPC.
For ARM I would prefer not to have a default at
Michael S. Tsirkin m...@redhat.com writes:
On Mon, May 20, 2013 at 12:57:47PM +0200, Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Generating acpi tables.
Cc'd a bunch of people who might be interested in this topic.
Unfortunately
On Tue, 2013-05-21 at 13:55 +0200, Andreas Färber wrote:
Hi,
Am 21.05.2013 13:33, schrieb Nicholas Thomas:
Migrating from:
/opt/qemu-1.4.1/bin/qemu-system-x86_64 -M pc -watchdog i6300esb
-watchdog-action reset [...]
to:
/opt/qemu-1.5.0/bin/qemu-system-x86_64 -M
On 05/21/2013 06:34 PM, Paolo Bonzini wrote:
Il 21/05/2013 12:27, Lei Li ha scritto:
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend
On Fri, 17 May 2013 16:23:51 +0200
Pavel Hrdina phrd...@redhat.com wrote:
On 25.4.2013 16:31, Luiz Capitulino wrote:
On Thu, 25 Apr 2013 16:29:45 +0200
Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Apr 25, 2013 at 09:51:47AM -0400, Luiz Capitulino wrote:
On Mon, 22 Apr 2013
On Tue, May 21, 2013 at 07:18:58AM -0500, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Mon, May 20, 2013 at 12:57:47PM +0200, Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Generating acpi tables.
On 05/21/2013 04:27 AM, Lei Li wrote:
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend called it 'ringbuf'. It should keep
consistent.
glibc wipes malloc(3) memory when the MALLOC_PERTURB_ environment
variable is set. The value of the environment variable determines the
bit pattern used to wipe memory. For more information, see
http://udrepper.livejournal.com/11429.html.
Set MALLOC_PERTURB_ for gtester and qemu-iotests. Note
Issuing the READ CAPACITY(10) command in the guest will cause QEMU
to update its knowledge of the maximum accessible LBA in the disk.
The recorded maximum LBA will be wrong if the disk is bigger than
1TB, because ldl_be_p returns a signed int.
When this is fixed, a latent bug will be unmasked.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/05/2013 14:38, Eric Blake ha scritto:
On 05/21/2013 04:27 AM, Lei Li wrote:
Now we have memory char device, but the backend name of it is a
little confusion. We actually register it by 'memory', but the
description in qemu-option, the name
1 - 100 of 252 matches
Mail list logo
