On 2 June 2013 06:46, Peter Cheung mcheun...@hotmail.com wrote:
I just tried to compile the latest qemu on Fedora 18 64 bits,
it is also fail. When i press c in gdb, the qemu won't start
running.
Good. This significantly increases the chances that somebody
will investigate.
But one thing
On Fri, May 31, 2013 at 01:45:55PM +0200, Laszlo Ersek wrote:
On 05/31/13 09:09, Jordan Justen wrote:
Why is updating the ACPI tables in seabios viewed as such a burden?
Either qemu does it, or seabios... (And, OVMF too, but I don't think
you guys are concerned with that. :)
I am :)
On Thu, May 30, 2013 at 10:34:26PM -0400, Kevin O'Connor wrote:
On Tue, May 28, 2013 at 07:53:09PM -0400, Kevin O'Connor wrote:
There were discussions on potentially introducing a middle component
to generate the tables. Coreboot was raised as a possibility, and
David thought it would be
Hi,
qemu is currently broken on ppc64. After applying the following patches
I am able to boot a ppc64 and x86-64 image successfully.
Anton
add2_i64 was adding the lower double word to the upper double word
of each input. Fix this so we add the lower double words, then the
upper double words with carry propagation.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Anton Blanchard an...@samba.org
---
sub2 has similar issues, I haven't fixed
rotr_i32 calculates the amount to left shift and puts it into a
temporary, but then doesn't use it when doing the shift.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: b/tcg/ppc64/tcg-target.c
If our input and output is in the same register, bswap64 tries to
undo a rotate of the input. This just ends up rotating the output.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Anton Blanchard an...@samba.org
---
diff --git a/tcg/ppc64/tcg-target.c b/tcg/ppc64/tcg-target.c
index 0fcf2b5..64fb0af
The rldcl instruction doesn't have an sh field, so the minor opcode
of 8 is actually 4 when using the XO30 macro.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: b/tcg/ppc64/tcg-target.c
===
---
Il 01/06/2013 00:18, Richard Henderson ha scritto:
On 05/30/2013 02:16 PM, Paolo Bonzini wrote:
+static inline Int128 int128_rshift(Int128 a, int n)
+{
+return (Int128) { (a.lo n) | (a.hi (64 - n)), (a.hi n) };
+}
Produces wrong results for n == 0, since (a.hi 64) is undefined.
On Sat, 2013-06-01 at 14:13 +0200, Benoît Canet wrote:
Hello,
I may have soon the PF driver of an SR-IOV card to code and make work with
QEMU/KVM so I have the following questions.
In an AMD64 setup where QEMU use VFIO to passthrough the VFs of an SR-IOV card
to a guest will the
On 31 May 2013 23:18, Richard Henderson r...@twiddle.net wrote:
On 05/30/2013 02:16 PM, Paolo Bonzini wrote:
+static inline Int128 int128_rshift(Int128 a, int n)
+{
+return (Int128) { (a.lo n) | (a.hi (64 - n)), (a.hi n) };
+}
Produces wrong results for n == 0, since (a.hi 64) is
On Wed, May 29, 2013 at 10:33:54AM +0800, Amos Kong wrote:
On Tue, May 28, 2013 at 06:59:02PM -0400, Kevin O'Connor wrote:
On Tue, May 28, 2013 at 08:28:14PM +0800, Amos Kong wrote:
Bootindex string passed from qemu:
/q35-pcihost@i0cf8/ethernet@2/ethernet-phy@0
We match pci domain
Il 02/06/2013 16:18, Peter Maydell ha scritto:
On 31 May 2013 23:18, Richard Henderson r...@twiddle.net wrote:
On 05/30/2013 02:16 PM, Paolo Bonzini wrote:
+static inline Int128 int128_rshift(Int128 a, int n)
+{
+return (Int128) { (a.lo n) | (a.hi (64 - n)), (a.hi n) };
+}
Produces
On 2 June 2013 15:36, Paolo Bonzini pbonz...@redhat.com wrote:
This should work:
int64_t h;
if (!n) {
return a;
}
h = a.hi n;
This is undefined for n = 64.
if (n = 64) {
return (Int128) { h, h 63 };
} else {
return (Int128) { (a.lo n)
On Sun, Jun 02, 2013 at 05:29:45PM +0300, Gleb Natapov wrote:
On Wed, May 29, 2013 at 10:33:54AM +0800, Amos Kong wrote:
On Tue, May 28, 2013 at 06:59:02PM -0400, Kevin O'Connor wrote:
On Tue, May 28, 2013 at 08:28:14PM +0800, Amos Kong wrote:
Bootindex string passed from qemu:
On Wed, May 29, 2013 at 11:45:44AM +0300, Michael S. Tsirkin wrote:
On Tue, May 28, 2013 at 07:53:09PM -0400, Kevin O'Connor wrote:
On Thu, May 23, 2013 at 03:41:32PM +0300, Michael S. Tsirkin wrote:
Juan is not available now, and Anthony asked for
agenda to be sent early.
So here
On Sun, Jun 02, 2013 at 06:05:42PM +0300, Gleb Natapov wrote:
On Wed, May 29, 2013 at 11:45:44AM +0300, Michael S. Tsirkin wrote:
On Tue, May 28, 2013 at 07:53:09PM -0400, Kevin O'Connor wrote:
On Thu, May 23, 2013 at 03:41:32PM +0300, Michael S. Tsirkin wrote:
Juan is not available now,
Thanks a lot for the answer.
Best regards
Benoît
Le Sunday 02 Jun 2013 à 08:11:42 (-0600), Alex Williamson a écrit :
On Sat, 2013-06-01 at 14:13 +0200, Benoît Canet wrote:
Hello,
I may have soon the PF driver of an SR-IOV card to code and make work with
QEMU/KVM so I have the
shift128Right would give the wrong result for a shift count
between 64 and 127. This was never noticed because all of
our uses of this function are guaranteed not to use shift
counts in this range.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
Found by code inspection. This
On Thu, May 30, 2013 at 06:58:07PM +0800, 李春奇 Arthur Chunqi Li wrote:
Hi there,
I'm now reading codes of kvm-unit-tests and I found that some of the
test cases for x86 is only designed for x86_64 (including access.flat,
apic.flat, emulator.flat, idt_test.flat and so on). I wonder why these
On Sun, Jun 02, 2013 at 05:59:04PM +0300, Michael S. Tsirkin wrote:
On Sun, Jun 02, 2013 at 05:29:45PM +0300, Gleb Natapov wrote:
On Wed, May 29, 2013 at 10:33:54AM +0800, Amos Kong wrote:
On Tue, May 28, 2013 at 06:59:02PM -0400, Kevin O'Connor wrote:
On Tue, May 28, 2013 at 08:28:14PM
Now that the DMA APIs are unified, we move closer and closer to breaking
memory access from the BQL dependency. This series adds an API to
reference/unreference memory regions, which is not really needed only
for BQL-less memory access: the big lock can already be dropped between
Whenever memory regions are accessed outside the BQL, they need to be
preserved against hot-unplug. MemoryRegions actually do not have their
own reference count; they piggyback on a QOM object, their owner.
Add two functions to retrieve and specify the owner.
The setter function will affect the
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
include/exec/memory.h | 30 ++
memory.c | 14 ++
2 files changed, 44 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 457a53c..71df1e6 100644
---
Cc: Alex Williamson awill...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/misc/vfio.c | 8
1 file changed, 8 insertions(+)
diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
index a1f5803..3c0dc9f 100644
--- a/hw/misc/vfio.c
+++ b/hw/misc/vfio.c
@@ -1156,6 +1156,7 @@
ACPI regions are added directly to the I/O address space, without
going through BARs. Thus they need the owner to be set directly.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/acpi/ich9.c | 1 +
hw/acpi/piix4.c | 5 +
hw/isa/apm.c| 1 +
3 files changed, 7 insertions(+)
diff
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/pci/pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index fa30110..2456075 100644
--- a/hw/pci/pci.c
+++ b/hw/pci/pci.c
@@ -914,6 +914,8 @@ void pci_register_bar(PCIDevice *pci_dev, int region_num,
Once address_space_translate will be callable out of the big QEMU
lock, the returned MemoryRegion will be unprotected as soon as
address_space_translate terminates. Avoid this by adding a reference to
the region, and dropping it in the caller of address_space_translate.
Signed-off-by: Paolo
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/core/sysbus.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/core/sysbus.c b/hw/core/sysbus.c
index 9004d8c..788696b 100644
--- a/hw/core/sysbus.c
+++ b/hw/core/sysbus.c
@@ -115,6 +115,8 @@ void sysbus_init_mmio(SysBusDevice *dev,
Add ref/unref calls at the following places:
- places where memory regions are stashed by a listener and
used outside the BQL (including in Xen or KVM).
- memory_region_find callsites
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c| 6 +-
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/isa/isa-bus.c | 2 ++
include/exec/ioport.h | 3 +++
ioport.c | 10 ++
3 files changed, 15 insertions(+)
diff --git a/hw/isa/isa-bus.c b/hw/isa/isa-bus.c
index 7860b17..d263d0f 100644
--- a/hw/isa/isa-bus.c
+++
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/char/serial-pci.c | 1 +
hw/misc/pc-testdev.c | 7 +++
2 files changed, 8 insertions(+)
diff --git a/hw/char/serial-pci.c b/hw/char/serial-pci.c
index 2138e35..6b6106b 100644
--- a/hw/char/serial-pci.c
+++ b/hw/char/serial-pci.c
@@
Cc: Gerd Hoffman kra...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/display/cirrus_vga.c | 19 ++-
hw/display/qxl.c| 6 --
hw/display/vga-isa-mm.c | 2 +-
hw/display/vga-isa.c| 4 ++--
hw/display/vga-pci.c| 5 +++--
hw/display/vga.c
It will be needed in the next patch.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c| 35 +--
include/exec/cpu-common.h | 2 +-
target-i386/kvm.c | 4 ++--
3 files changed, 24 insertions(+), 17 deletions(-)
diff --git
Cc: Alex Williamson awill...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/i386/kvm/pci-assign.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/hw/i386/kvm/pci-assign.c b/hw/i386/kvm/pci-assign.c
index ff85590..4b1c2d9 100644
--- a/hw/i386/kvm/pci-assign.c
This function is not used outside the iothread mutex, so it
can use ram_list.mru_block.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/exec.c b/exec.c
index bf287cb..9fd4c90 100644
--- a/exec.c
+++
On Sun, Jun 02, 2013 at 06:09:50PM +0300, Michael S. Tsirkin wrote:
On Sun, Jun 02, 2013 at 06:05:42PM +0300, Gleb Natapov wrote:
On Wed, May 29, 2013 at 11:45:44AM +0300, Michael S. Tsirkin wrote:
On Tue, May 28, 2013 at 07:53:09PM -0400, Kevin O'Connor wrote:
On Thu, May 23, 2013 at
The iothread mutex might be released between map and unmap, so the
mapped region might disappear.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/exec.c b/exec.c
index 39324ba..538aa9e 100644
---
On Sun, Jun 02, 2013 at 06:40:43PM +0300, Gleb Natapov wrote:
On Sun, Jun 02, 2013 at 06:09:50PM +0300, Michael S. Tsirkin wrote:
On Sun, Jun 02, 2013 at 06:05:42PM +0300, Gleb Natapov wrote:
On Wed, May 29, 2013 at 11:45:44AM +0300, Michael S. Tsirkin wrote:
On Tue, May 28, 2013 at
On 2 June 2013 16:43, Paolo Bonzini pbonz...@redhat.com wrote:
+/**
+ * memory_region_ref: Add 1 to a memory region's reference count
+ *
+ * Whenever memory regions are accessed outside the BQL, they need to be
+ * preserved against hot-unplug. MemoryRegions actually do not have their
+ *
On 2 June 2013 16:43, Paolo Bonzini pbonz...@redhat.com wrote:
-int qemu_ram_addr_from_host(void *ptr, ram_addr_t *ram_addr);
+MemoryRegion *qemu_ram_addr_from_host(void *ptr, ram_addr_t *ram_addr);
ram_addr_t qemu_ram_addr_from_host_nofail(void *ptr);
This is weird, because now the _nofail
On 2 June 2013 16:43, Paolo Bonzini pbonz...@redhat.com wrote:
Reference counting the region piggybacks on reference counting of a QOM
object, the owner of the region. The owner API is designed so that
it will be called as little as possible. Unowned subregions will get a
region if
On 01/06/13 21:59, Blue Swirl wrote:
On Sat, Jun 1, 2013 at 11:41 AM, Mark Cave-Ayland
mark.cave-ayl...@ilande.co.uk wrote:
Commit d08151bf (conversion of tcx to the memory API) broke the 24-bit mode of
the tcx display adapter by accidentally passing in the final address of the
dirty region
Commit d08151bf (conversion of tcx to the memory API) broke the 24-bit mode of
the tcx display adapter by accidentally passing in the final address of the
dirty region to memory_region_reset_dirty() instead of its size.
Signed-off-by: Mark Cave-Ayland mark.cave-ayl...@ilande.co.uk
---
Thanks, applied.
On Sun, Jun 2, 2013 at 4:23 PM, Mark Cave-Ayland
mark.cave-ayl...@ilande.co.uk wrote:
Commit d08151bf (conversion of tcx to the memory API) broke the 24-bit mode of
the tcx display adapter by accidentally passing in the final address of the
dirty region to
Newer architectures may only implement the getdents64 syscall, not
getdents. Provide an implementation of getdents in terms of getdents64
so that we can run getdents-using targets on a getdents64-only host.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
Guess which exciting new
On 20 May 2013 18:21, Richard Henderson r...@twiddle.net wrote:
On 05/19/2013 09:30 AM, Ed Maste wrote:
That is, it just changes the start address. Is this generally the
only difference between QEMU's linker scripts and system built-ins?
Yes.
So for a new architecture how do we determine
On Fri, May 31, 2013 at 04:52:18PM +0800, Xiao Guangrong wrote:
Luiz Capitulino reported that guest refused to boot and qemu
complained with:
kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument
It is caused by commit 235e8982ad that did double free for the memslot
so
Il 02/06/2013 16:50, Peter Maydell ha scritto:
On 2 June 2013 15:36, Paolo Bonzini pbonz...@redhat.com wrote:
This should work:
int64_t h;
if (!n) {
return a;
}
h = a.hi n;
This is undefined for n = 64.
Yes, it has to be a.hi (n 63).
I would suggest looking
Reviewed-by: Jordan Justen jordan.l.jus...@intel.com
On Fri, May 31, 2013 at 1:52 AM, Xiao Guangrong
xiaoguangr...@linux.vnet.ibm.com wrote:
Luiz Capitulino reported that guest refused to boot and qemu
complained with:
kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument
On Thu, 05/30 18:00, Dongxu Wang wrote:
It will introduce a new file format: add-cow.
The add-cow file format makes it possible to perform copy-on-write on top of
a raw disk image. When we know that no backing file clusters remain visible
(e.g. we have streamed the entire image and copied
On Thu, 05/30 18:00, Dongxu Wang wrote:
From: Dong Xu Wang wdon...@linux.vnet.ibm.com
Document for add-cow format, the usage and spec of add-cow are
introduced.
v18-v19:
1) backing_fmt and image_fmt NUL-terminated.
2) other fix.
V17-V18:
1) remove version field.
2) header size is
On 2013/6/3 9:48, Fam Zheng wrote:
On Thu, 05/30 18:00, Dongxu Wang wrote:
From: Dong Xu Wang wdon...@linux.vnet.ibm.com
Document for add-cow format, the usage and spec of add-cow are
introduced.
v18-v19:
1) backing_fmt and image_fmt NUL-terminated.
2) other fix.
V17-V18:
1) remove version
于 2013-5-31 21:19, Luiz Capitulino 写道:
On Fri, 31 May 2013 21:04:10 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013-5-30 10:41, Wenchao Xia 写道:
于 2013-5-27 23:41, Kevin Wolf 写道:
Am 25.05.2013 um 05:09 hat Wenchao Xia geschrieben:
These patches are the common part of my hmp/qmp
Anthony Liguori anth...@codemonkey.ws writes:
Michael S. Tsirkin m...@redhat.com writes:
On Thu, May 30, 2013 at 08:40:47AM -0500, Anthony Liguori wrote:
Stefan Hajnoczi stefa...@gmail.com writes:
On Thu, May 30, 2013 at 7:23 AM, Rusty Russell ru...@rustcorp.com.au
wrote:
Anthony
This series lets qmp interface show delaied info, including internal snapshot
/backing chain on all block device at runtime, which helps management stack and
human user, by retrieving exactly the same info of what qemu sees.
Example:
- { execute: query-block }
- {
return:[
{
New member *backing-image is added to reflect the backing chain
status.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qapi.c |7 +++
qapi-schema.json |5 -
2 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/block/qapi.c b/block/qapi.c
index
This patch adds function bdrv_query_snapshot_info_list(), which will
retrieve snapshot info of an image in qmp object format. The implementation
is based on the code moved from qemu-img.c with modification to fit more
for qmp based block layer API.
Signed-off-by: Wenchao Xia
This patch adds function bdrv_query_image_info(), which will
retrieve image info in qmp object format. The implementation is
based on the code moved from qemu-img.c, but uses block layer
function to get snapshot info.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qapi.c
Now human monitor can show image details, include internal
snapshot and backing chain info for every block device.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
hmp.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/hmp.c b/hmp.c
index
With these parameters, user can choose the information to be showed,
to avoid message flood in the monitor.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
Reviewed-by: Kevin Wolf kw...@redhat.com
---
hmp.c | 25 -
monitor.c |7 ---
2 files changed, 20
Now image info will be retrieved as an embbed json object inside
BlockDeviceInfo, backing chain info and all related internal snapshot
info can be got in the enhanced recursive structure of ImageInfo.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qapi.c | 43
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Some cosmetics, refactored to use util/fifo8 for the FIFO8, then
factored out some common code.
Tested as working on petalogix-ml605 machine model + Linux (has
coverage of serial fifo usage).
Peter Crosthwaite (3):
char/serial: cosmetic
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Some cosmetic fixes to char/serial fixing some checkpatch errors.
Cc: qemu-triv...@nongnu.org
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
Needed for the next patch to pass checkpatch. Done as sep patch to not
obscure
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Use the generic Fifo8 helper provided by QEMU, rather than re-implement
privately.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
hw/char/serial.c | 98 +---
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
These three lines are common to both FIFO and regular mode. Just factor
them out to outside the if rather than replicate the same lines inside
both if and else.
Cc: qemu-triv...@nongnu.org
Signed-off-by: Peter Crosthwaite
On 06/01/13 01:01, Jordan Justen wrote:
On Fri, May 31, 2013 at 2:32 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
I guess -bios would load coreboot. Coreboot would siphon the data
necessary for ACPI table building through the current (same) fw_cfg
bottleneck, build the tables,
Yes.
Oh, almost forgot it,
Peter, what about the version?
Thanks!
在 2013-05-06一的 13:55 +0800，liguang写道：
for helper_{lsl, lar, verr, verw}, there are
common parts, so move them outside, and then
call this new helper-helper function.
Signed-off-by: liguang lig.f...@cn.fujitsu.com
---
v2: change
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
Some trivial fixes to memory API.
Peter Crosthwaite (3):
memory: Fix comment typo
memory: as_update_topology_pass: Improve comments
memory: render_memory_region: factor out fr constant setters
memory.c | 19 ---
1 file
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
s/ajacent/adjacent
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/memory.c b/memory.c
index 5cb8f4a..60e033b 100644
--- a/memory.c
+++ b/memory.c
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
These comments we're a little difficult to read. First one had
incorrect parenthesis. The part about attributes changing is
really applicable to the region being 'in both' rather than 'in
new'
Second comment has an obscure parenthetic about
From: Peter Crosthwaite peter.crosthwa...@xilinx.com
These 4 replicated lines set properties of fr that are constant over
the course of the function. Factor out their repeated setting (and also
guards against them being set multiple times in the loop below).
Signed-off-by: Peter Crosthwaite
Hi,
Is it valid to have cache=none and discard=unmap together? I notice
that when I have cache=none the fstrim operations inside of my guests
gives me an error and i get this from the sys filesystem:
[root@guest ~]# cat /sys/block/sdb/queue/discard*
4096
0
0
This wasn't very obvious to me to
Dear all,
I've a scene,
I have many host nodes with linux kernels, and I want to boot one guest
OS on all these nodes use QEMU/KVM. In order that I can use all the
physical CPUs and Mems distributed on these linux nodes, and the Guest
looks like a SMP or shared-memory system.
How can I use
74 matches
Mail list logo
