On 02/08/2012 04:27 PM, Avi Kivity wrote:
+static void core_log_stop(MemoryListener *listener,
+ MemoryRegionSection *section)
+{
+}
+
+static void core_log_sync(MemoryListener *listener,
+ MemoryRegionSection *section)
+{
+}
+
Why not wrapping
Am Thu, 9 Feb 2012 11:26:09 +1100
schrieb David Gibson :
> On Wed, Feb 08, 2012 at 02:27:35PM +0100, Thomas Huth wrote:
> > Am Wed, 8 Feb 2012 21:48:40 +1100
> > schrieb David Gibson :
> >
> > > On Wed, Feb 08, 2012 at 10:54:21AM +0400, malc wrote:
> > > > On Wed, 8 Feb 2012, David Gibson wrote:
On 02/09/2012 03:40 AM, Xin Tong wrote:
can you show me where these threads get created in the qemu code ?
It's in posix-aio-compat.c. The code is invoked by block/raw-posix.c.
Paolo
On 02/09/2012 06:46 AM, Hu Tao wrote:
> >I've re-tested today, with host kernel 2.6.35.6-45.fc14.x86_64,
> >2.6.32-71.el6.x86_64, 3.1.0 and 3.3.0-rc1+, qemu version and guest
> >configuration remain the same, including guest kernel. It apears
> >that the problem appears only when the host ker
On 02/09/2012 10:18 AM, Evgeny Voevodin wrote:
On 02/09/2012 10:15 AM, Peter Maydell wrote:
On 9 February 2012 06:13, Evgeny Voevodin wrote:
It seems that we have to rebase our exynos boards again ). So, am I
right
supposing that exynos will not be applied until all QOM patch sets
landed?
Ant
Drop the legacy init function arm_sysctl_init(), since it has no
users left any more. This allows us to drop the awkward '1' from
the actual device init function.
Signed-off-by: Peter Maydell
---
The legacy function also had the 'set property after init' bug (in fact
this is the original source f
On 02/09/2012 10:15 AM, Peter Maydell wrote:
On 9 February 2012 06:13, Evgeny Voevodin wrote:
It seems that we have to rebase our exynos boards again ). So, am I right
supposing that exynos will not be applied until all QOM patch sets landed?
Anthony claims there aren't any more QOM patchsets
On 9 February 2012 06:13, Evgeny Voevodin wrote:
> It seems that we have to rebase our exynos boards again ). So, am I right
> supposing that exynos will not be applied until all QOM patch sets landed?
Anthony claims there aren't any more QOM patchsets which touch all the
files in the tree, so no
On 02/09/2012 10:04 AM, Peter Maydell wrote:
On 9 February 2012 05:16, Evgeny Voevodin wrote:
Since last QOM patch set landed into master, realview-pbx-a9,
realview-eb-mpcore (suppose that other too) abort with error:
qemu/hw/qdev-properties.c:1161: qdev_prop_set_uint32: Assertion `!errp'
fail
On 9 February 2012 05:16, Evgeny Voevodin wrote:
> Since last QOM patch set landed into master, realview-pbx-a9,
> realview-eb-mpcore (suppose that other too) abort with error:
>
> qemu/hw/qdev-properties.c:1161: qdev_prop_set_uint32: Assertion `!errp'
> failed.
Incidentally, this is a rather unh
The ARM devboard models (vexpress-a9, realview, versatilepb, etc)
were accidentally trying to set one of the arm_sysctl properties
after device init. This has now become a fatal error; set the property
before device init where it should be done instead.
Signed-off-by: Peter Maydell
---
If somebod
On 9 February 2012 05:16, Evgeny Voevodin wrote:
> Since last QOM patch set landed into master, realview-pbx-a9,
> realview-eb-mpcore (suppose that other too) abort with error:
>
> qemu/hw/qdev-properties.c:1161: qdev_prop_set_uint32: Assertion `!errp'
> failed.
> Aborted
The realview etc board m
On Tue, Jan 31, 2012 at 01:36:04PM +0100, Paolo Bonzini wrote:
> On 01/30/2012 10:33 AM, Hu Tao wrote:
> >>> I cannot reproduce this with a 100G qcow2 image (created with
> >>> "qemu-img create scsi.qcow2 100G" just before launching the host),
> >>> with a partition starting at sector 2048 and e
Since last QOM patch set landed into master, realview-pbx-a9,
realview-eb-mpcore (suppose that other too) abort with error:
qemu/hw/qdev-properties.c:1161: qdev_prop_set_uint32: Assertion `!errp'
failed.
Aborted
Bisect result:
9b170e60adc6dc01564128cf09f96ec923ed6526 is the first bad commit
In kvm-all.c we store an ioctl cmd number in the irqchip_inject_ioctl field
of KVMState, which has type 'int'. This seems to make sense since the
ioctl() man page says that the cmd parameter has type int.
However, the kernel treats ioctl numbers as unsigned - sys_ioctl() takes an
unsigned int, an
On Wed, Feb 08, 2012 at 04:27:48PM +0100, Joerg Roedel wrote:
> On Wed, Feb 01, 2012 at 03:46:52PM +1100, David Gibson wrote:
> > In order to safely drive a device with a userspace driver, or to pass
> > it through to a guest system, we must first make sure that the device
> > is isolated in such a
Signed-off-by: Wen Congyang
---
dump.c | 206 --
hmp-commands.hx |6 +-
hmp.c| 13 +++-
memory_mapping.c | 27 +++
memory_mapping.h |2 +
qapi-schema.json |6 ++-
qmp-commands.hx |4 +-
7 files ch
The command dump does not support to dump while vm is running. If the user
resume
the vm, we should auto cancel dumping and set the status to failed.
Signed-off-by: Wen Congyang
---
dump.c | 19 +++
vl.c |5 +++--
2 files changed, 22 insertions(+), 2 deletions(-)
diff -
Add API to allow the user to query dumping status.
Signed-off-by: Wen Congyang
---
dump.c | 32
hmp-commands.hx |2 ++
hmp.c| 17 +
hmp.h|1 +
monitor.c|7 +++
qapi-schema.json | 26
Add API to allow the user to control dumping speed
Signed-off-by: Wen Congyang
---
dump.c | 12
hmp-commands.hx | 15 +++
hmp.c|6 ++
hmp.h|1 +
qapi-schema.json | 15 +++
qmp-commands.hx | 22 ++
Add API to allow the user to cancel the current dumping.
Signed-off-by: Wen Congyang
---
dump.c | 13 +
hmp-commands.hx | 14 ++
hmp.c|5 +
hmp.h|1 +
qapi-schema.json | 13 +
qmp-commands.hx | 21 +++
Let the user to choose whether to block other monitor command while dumping.
Signed-off-by: Wen Congyang
---
dump.c | 12
hmp-commands.hx |8
hmp.c|3 ++-
qapi-schema.json |3 ++-
qmp-commands.hx |7 ---
5 files changed, 20 inse
The new monitor command dump may take long time to finish. So we need run it
at the background.
Signed-off-by: Wen Congyang
---
dump.c | 155
1 files changed, 136 insertions(+), 19 deletions(-)
diff --git a/dump.c b/dump.c
index
Signed-off-by: Wen Congyang
---
Makefile.target |8 +-
dump.c | 590 ++
dump.h |3 +
hmp-commands.hx | 16 ++
hmp.c|9 +
hmp.h|1 +
monitor.c|3 +
qapi-schema.json |
Dump info contains: endian, class and architecture. The next
patch will use these information to create vmcore.
Signed-off-by: Wen Congyang
---
cpu-all.h |3 +++
dump.h | 10 ++
target-i386/arch-dump.c | 34 ++
3 file
Crash needs extra memory mapping to determine phys_base.
Signed-off-by: Wen Congyang
---
cpu-all.h |2 ++
target-i386/arch-dump.c | 43 +++
2 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/cpu-all.h b/cpu-all.h
index efb5
The core file contains register's value. These APIs write registers to
core file, and them will be called in the following patch.
Signed-off-by: Wen Congyang
---
cpu-all.h |6 +
target-i386/arch-dump.c | 243 +++
2 files changed, 249
Add API to get all virtual address and physical address mapping.
If there is no virtual address for some physical address, the virtual
address is 0.
Signed-off-by: Wen Congyang
---
memory_mapping.c | 65 ++
memory_mapping.h |1 +
2 files
Walk cpu's page table and collect all virtual address and physical address
mapping.
Then, add these mapping into memory mapping list.
Signed-off-by: Wen Congyang
---
Makefile.target |2 +-
cpu-all.h |7 ++
target-i386/arch-dump.c | 254
This API will be used in the following patch.
Signed-off-by: Wen Congyang
---
cpu-common.h |2 ++
exec.c | 16
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/cpu-common.h b/cpu-common.h
index a40c57d..d047137 100644
--- a/cpu-common.h
+++ b/cpu-commo
The memory mapping list stores virtual address and physical address mapping.
The folloing patch will use this information to create PT_LOAD in the vmcore.
Signed-off-by: Wen Congyang
---
Makefile.target |1 +
memory_mapping.c | 130 ++
me
Sync command needs these two APIs to suspend/resume monitor.
Signed-off-by: Wen Congyang
---
monitor.c | 27 +++
monitor.h |2 ++
2 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index 11639b1..7e72739 100644
--- a/monitor.c
+++
Hi, all
'virsh dump' can not work when host pci device is used by guest. We have
discussed this issue here:
http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html
We have determined to introduce a new command dump to dump memory. The core
file's format can be elf.
Note:
1. The gue
can you show me where these threads get created in the qemu code ?
Thanks
Xin
On Tue, Feb 7, 2012 at 5:25 AM, Stefan Hajnoczi wrote:
> 2012/2/7 陳韋任 :
>> Hi Stefan,
>>
>> Thanks for the explanation. :)
>>
>>> > Qemu 1.0 enable IO thread by default, I think that's why you can see
>>> > ther
Alrighty,
So it seems like the bootloader as a device idea has some support, just
need to work out a few implementaiton details. It seems the consensus is
that machine models will instantiate the device. The latest idea is the
machine model will pass some of core props to the bootloader while othe
Does the same happen in a release version of Qemu?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/928204
Title:
build failure gentoo
Status in QEMU:
New
Bug description:
gcc 4.5.3, gentoo linu
On Wed, Feb 08, 2012 at 02:27:35PM +0100, Thomas Huth wrote:
> Am Wed, 8 Feb 2012 21:48:40 +1100
> schrieb David Gibson :
>
> > On Wed, Feb 08, 2012 at 10:54:21AM +0400, malc wrote:
> > > On Wed, 8 Feb 2012, David Gibson wrote:
> > >
> > > > From: Thomas Huth
> > > >
> > > > These instructions
> +static void i8042_isa_mouse_fake_event(void *opaque, int n, int level)
> {
> ISADevice *dev = opaque;
> KBDState *s = &(DO_UPCAST(ISAKBDState, dev, dev)->kbd);
>
> -ps2_mouse_fake_event(s->mouse);
> +if (level) {
> +ps2_mouse_fake_event(s->mouse);
> +}
> }
>...
> > starting your own toy kernel is a fun thing to do and there are many
> > tutorials out there on how to do it. Unfortunately when one wants to
> > write a kernel in 64bit it becomes much harder because one can't
> > compile 64bit code as elf32 image and converting a elf64 image to
> > elf32 form
On Wed, 8 Feb 2012, Stefan Weil wrote:
> Makefile, Makefile.hw, Makefile.target and libcacard/Makefile
> added GLIB_CFLAGS to QEMU_CFLAGS.
>
> Makefile.objs does this, too, and is included by all other
> Makefiles, so GLIB_CFLAGS were added twice (reported by malc).
>
Thank you.
If nobody obje
On 09.02.2012, at 00:54, Scott Wood wrote:
> On 02/08/2012 05:42 PM, Alexander Graf wrote:
>>
>> On 09.02.2012, at 00:29, Scott Wood wrote:
>>
>>> On 02/07/2012 04:57 PM, Alexander Graf wrote:
Eh, this patch:
diff --git a/tcg/ppc/tcg-target.c b/tcg/ppc/tcg-target.c
index f5
On 02/08/2012 05:42 PM, Alexander Graf wrote:
>
> On 09.02.2012, at 00:29, Scott Wood wrote:
>
>> On 02/07/2012 04:57 PM, Alexander Graf wrote:
>>> Eh, this patch:
>>>
>>> diff --git a/tcg/ppc/tcg-target.c b/tcg/ppc/tcg-target.c
>>> index f5d9bf3..f9793e6 100644
>>> --- a/tcg/ppc/tcg-target.c
>>>
> The purpose of the "helper" option for "-net tap" isn't obvious
> based on its name. This patch changes the option name to
> "bridgehelper" to make its purpose more self-documenting.
>
> With this patch, a typical invocation will be similar to one of the
> following (where the default bridge is
On 09.02.2012, at 00:29, Scott Wood wrote:
> On 02/07/2012 04:57 PM, Alexander Graf wrote:
>>
>> On 07.02.2012, at 23:29, Brad Smith wrote:
>>
>>> On 07/02/12 5:12 PM, malc wrote:
On Tue, 7 Feb 2012, Alexander Graf wrote:
>
> On 07.02.2012, at 22:12, malc wrote:
>
>
On 02/07/2012 04:57 PM, Alexander Graf wrote:
>
> On 07.02.2012, at 23:29, Brad Smith wrote:
>
>> On 07/02/12 5:12 PM, malc wrote:
>>> On Tue, 7 Feb 2012, Alexander Graf wrote:
>>>
On 07.02.2012, at 22:12, malc wrote:
> On Tue, 7 Feb 2012, Alexander Graf wrote:
>
>>
>>>
On 02/08/2012 07:27 AM, Avi Kivity wrote:
> This patchset makes the memory core (memory.c) talk to the backend (in exec.c)
> via a MemoryListener instead of named functions.
>
> While the motivation for this is to simplify the memory core, it also enables
> optimizing accelerators some more (by ha
On Wed, 2012-02-08 at 16:27 +0100, Joerg Roedel wrote:
> Again, device grouping is done by the IOMMU drivers, so this all
> belongs
> into the generic iommu-code rather than the driver core.
>
> I think it makes sense to introduce a device->iommu pointer which
> depends on CONFIG_IOMMU_API and put
Makefile, Makefile.hw, Makefile.target and libcacard/Makefile
added GLIB_CFLAGS to QEMU_CFLAGS.
Makefile.objs does this, too, and is included by all other
Makefiles, so GLIB_CFLAGS were added twice (reported by malc).
Signed-off-by: Stefan Weil
---
Makefile |2 --
Makefile.hw
On Wed, 2012-02-08 at 16:27 +0100, Joerg Roedel wrote:
> Again, device grouping is done by the IOMMU drivers, so this all
> belongs
> into the generic iommu-code rather than the driver core.
Except that there isn't really a "generic iommu code"... discovery,
initialization & matching of iommu vs.
Does anyone use gdb testsuite with remote target of qemu in linux-user mode?
I see no mention of qemu as a remote simulator in dejagnu, or in gdb/testsuite.
I threw together a qemu.exp to do this, and it seems to work OK everywhere
except
with mi-support.exp, which does not appear to have infrast
qmp_query_balloon() and qmp_balloon() perform the same check, move it
to check_kvm_sync_mmu().
Signed-off-by: Luiz Capitulino
---
balloon.c | 15 +++
1 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/balloon.c b/balloon.c
index b32b487..d340ae3 100644
--- a/balloon.c
This commit adds a QMP API for the guest provided memory statistics
(long disabled by commit 07b0403dfc2b2ac179ae5b48105096cc2d03375a).
The approach taken by the original commit
(625a5befc2e3200b396594f002218d235e375da5) was to extend the
query-balloon command. It introduced a severe bug though: q
It has never been used and next patches will introduce a new,
usable interface.
Note that dropping this won't break compatibility because all
fields are optional.
Signed-off-by: Luiz Capitulino
---
hmp.c| 25 +
qapi-schema.json | 21 +
Next commit will introduce the QEMUBalloonStats type, it can cause
confusion with QEMUBalloonStatus. Also, QEMUBalloonInfo matches
better with BalloonInfo, which is the type used to return balloon
information in QMP.
Signed-off-by: Luiz Capitulino
---
balloon.c | 18 +
Signed-off-by: Luiz Capitulino
---
balloon.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/balloon.h b/balloon.h
index b60fd5d..17fe300 100644
--- a/balloon.h
+++ b/balloon.h
@@ -14,7 +14,6 @@
#ifndef _QEMU_BALLOON_H
#define _QEMU_BALLOON_H
-#include "monitor.h"
#i
Commit d72f326431e280a619a0fd55e27d3737747f8178 converted the
balloon command to the QAPI, but forgot to convert one qerror_report()
usage. Fix it.
Signed-off-by: Luiz Capitulino
---
balloon.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/balloon.c b/balloon.c
index 0
This series re-enables the balloon memory statistics feature disabled
long ago by commit 11724ff.
The feature has been disabled because it added a severe bug: query-balloon
would hang if the guest didn't respond. This, in turn, would also cause a
hang in libvirt.
To avoid that bug, the solution i
From: Jan Kiszka
To both avoid that kvm_irqchip_in_kernel always has to be paired with
kvm_enabled and that the former ends up in a function call, implement it
like the latter. This means keeping the state in a global variable and
defining kvm_irqchip_in_kernel as a preprocessor macro.
Signed-of
The following changes since commit cf4dc461a4cfc3e056ee24edb26154f4d34a6278:
Restore consistent formatting (2012-02-07 22:11:04 +0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Jan Kiszka (3):
kvm: Allow to set shadow MMU size
From: Jan Kiszka
Also in case of loading pre-vmstate machines, we also need to open-code
the reading of the timer expires value and instead call the post_load
callback to apply it (or not). This fixes loading of legacy states into
the KVM APIC.
Reported-by: Paolo Bonzini
Signed-off-by: Jan Kisz
From: Jan Kiszka
Introduce the KVM-specific machine option kvm_shadow_mem. It allows to
set a custom shadow MMU size for the virtual machine. This is useful for
stress testing e.g.
Only x86 supports this for now, but it is in principle a generic
concept for all targets with shadow MMUs.
Signed-
qemu 0.11.1 package:
CCx86_64-linux-user/host-utils.o
CCx86_64-linux-user/tcg/tcg.o
CCx86_64-linux-user/tcg/tcg-runtime.o
CCx86_64-linux-user/fpu/softfloat-native.o
CCx86_64-linux-user/op_helper.o
{standard input}: Assembler messages:
{standard input}:3270769: Warning:
On Sun, Feb 05, 2012 at 11:46:26AM +0100, Jan Kiszka wrote:
> This adds another piece of qemu-kvm to upstream: The accelerated
> in-kernel model of the i8254. It does this in the same fashion as the
> interrupt controllers were already introduced. And it even has one bug
> less than qemu-kvm: PC sp
Signed-off-by: Paolo Bonzini
---
configure | 39 +++
1 files changed, 39 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 763db24..0f305cb 100755
--- a/configure
+++ b/configure
@@ -119,6 +119,7 @@ curl=""
curses=""
docs=""
fdt=""
+d
We need to use O_EXCL in order to suppress event generation in the
kernel. However, O_EXCL by definition fails when the CD-ROM drive
is mounted. Automatically unmount it when it is passed through to
the guest.
Signed-off-by: Paolo Bonzini
---
Makefile.objs|3 +
block.c
We will add CDROM-specific fields in the next patch, reuse the space
in the struct.
Signed-off-by: Paolo Bonzini
---
block/raw-posix.c | 38 +-
1 files changed, 21 insertions(+), 17 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index 2a5b6
Try to open the disk O_EXCL so that udev will not receive eject
request and media change events. These will work fine with SCSI
passthrough.
With IDE and scsi-disk the user will need to use the monitor in order
to eject the disk and put it back (respectively with the eject and
change commands).
There is no need to try matching device names; using ioctls is more
effective. So, always return a low priority from the generic
hdev_probe_device and let the ioctl tests override it.
Signed-off-by: Paolo Bonzini
---
block/raw-posix.c | 12 +++-
1 files changed, 3 insertions(+), 9 del
This series makes it possible to use CD drives reliably with scsi-block.
IDE and scsi-disk require more work, because the eject button is not
usable.
CD drives are unmounted at VM start and opened exclusively. The locking
state is saved and restored for extra kindness. However, drives are not
re
> >register_pio_hook_ptr_r(PIO_IDE, SIZE_BYTE,&s->cmd[0]);
> >for (i = 1; i< 7; i++) {
> > register_pio_hook_ptr_r(PIO_IDE + i, SIZE_BYTE,&s->cmd[i]);
> > register_pio_hook_ptr_w(PIO_IDE + i, SIZE_BYTE,&s->cmd[i]);
> >}
>
> You can't easily serialize updates to that address
> If the fd overhead really is a problem, perhaps the fd could be retained
> for setup operations, and omitted only on calls that require a vcpu to
> have been already set up on the current thread?
Quite frankly I'd like to have an fd because it means you've got a
meaningful way of ensuring that i
On 02/07/2012 06:28 AM, Anthony Liguori wrote:
> On 02/06/2012 01:46 PM, Scott Wood wrote:
>> On 02/03/2012 04:52 PM, Anthony Liguori wrote:
>>> On 02/03/2012 12:07 PM, Eric Northup wrote:
How would the ability to use sys_kvm_* be regulated?
>>>
>>> Why should it be regulated?
>>>
>>> It's not
On Sun, Feb 05, 2012 at 12:45:20PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Also in case of loading pre-vmstate machines, we also need to open-code
> the reading of the timer expires value and instead call the post_load
> callback to apply it (or not). This fixes loading of legacy states i
On 02/08/2012 10:15 AM, Paul Brook wrote:
Ok, that sounds more workable :). So i would add my initrd_addr property to
the bootloader as a qdev prop as I suggested before, then something like:
qemu-system-arm -M verstailepb -property
/foo/bar/arm_linux_loader.0,initrd_addr=0x1000
Yes.
Ther
On 02/08/2012 10:03 AM, Peter Crosthwaite wrote:
2012/2/9 Paul Brook
So here are some of the problems im trying to solve with the bootloader:
Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
assumed to be not kernels).
Change the kernel, initrd and dtb load address on
> Ok, that sounds more workable :). So i would add my initrd_addr property to
> the bootloader as a qdev prop as I suggested before, then something like:
>
> qemu-system-arm -M verstailepb -property
> /foo/bar/arm_linux_loader.0,initrd_addr=0x1000
Yes.
There are various implementation/syntax
2012/2/9 Paul Brook
> > So here are some of the problems im trying to solve with the bootloader:
> >
> > Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
> > assumed to be not kernels).
> > Change the kernel, initrd and dtb load address on the command line.
> > Use my own
> So here are some of the problems im trying to solve with the bootloader:
>
> Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
> assumed to be not kernels).
> Change the kernel, initrd and dtb load address on the command line.
> Use my own SMP secondary bootloop.
>
> My
It can be derived from the MemoryRegion itself (which is why it is not
used there).
Signed-off-by: Avi Kivity
---
exec-obsolete.h |2 +-
exec.c |2 +-
memory.c|4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/exec-obsolete.h b/exec-obsolete.h
in
All functionality has been moved to various MemoryListeners.
Signed-off-by: Avi Kivity
---
memory.c | 56 ++--
1 files changed, 2 insertions(+), 54 deletions(-)
diff --git a/memory.c b/memory.c
index 4e7a90b..4f854d4 100644
--- a/memory.c
++
This patchset makes the memory core (memory.c) talk to the backend (in exec.c)
via a MemoryListener instead of named functions.
While the motivation for this is to simplify the memory core, it also enables
optimizing accelerators some more (by having a tcg MemoryListener to do tcg
specific core) a
On 02/08/2012 09:36 AM, Andreas Färber wrote:
Am 08.02.2012 16:23, schrieb Anthony Liguori:
On 02/08/2012 09:04 AM, malc wrote:
On Wed, 8 Feb 2012, Andreas F?rber wrote:
Arbitrarily reformatting your files is not okay. If you want a different
formatting, you need to fix checkpatch.pl first to
Am 08.02.2012 16:23, schrieb Anthony Liguori:
> On 02/08/2012 09:04 AM, malc wrote:
>> On Wed, 8 Feb 2012, Andreas F?rber wrote:
>>
>>> Arbitrarily reformatting your files is not okay. If you want a different
>>> formatting, you need to fix checkpatch.pl first to not error on that
>>> formatting in
On 02/08/2012 05:27 PM, Avi Kivity wrote:
> This patchset makes the memory core (memory.c) talk to the backend (in exec.c)
> via a MemoryListener instead of named functions.
>
> While the motivation for this is to simplify the memory core, it also enables
> optimizing accelerators some more (by hav
This transforms memory.c into a library which can then be unit tested
easily, by feeding it inputs and listening to its outputs.
Signed-off-by: Avi Kivity
---
exec-obsolete.h |3 ++
exec.c | 75 +++
memory.c| 27 +--
Am 08.02.2012 16:04, schrieb malc:
> On Wed, 8 Feb 2012, Andreas F?rber wrote:
>
>> Arbitrarily reformatting your files is not okay. If you want a different
>> formatting, you need to fix checkpatch.pl first to not error on that
>> formatting in your files.
>
> It was always formatter like this (
.readonly cannot be obtained from the MemoryRegion, since it is
inherited from aliases (so you can have a MemoryRegion mapped RW
at one address and RO at another). Record it in a MemoryRegionSection
for listeners.
Signed-off-by: Avi Kivity
---
memory.c |5 +
memory.h |2 ++
2 files
memory_region_set_offset() will be going away soon, so don't use it.
Use an alias instead.
Signed-off-by: Avi Kivity
---
ioport.c | 25 +++--
ioport.h |1 +
2 files changed, 20 insertions(+), 6 deletions(-)
diff --git a/ioport.c b/ioport.c
index 36fa3a4..505b252 100644
Signed-off-by: Avi Kivity
---
memory.c | 54 +++---
1 files changed, 19 insertions(+), 35 deletions(-)
diff --git a/memory.c b/memory.c
index 382dded..6afe414 100644
--- a/memory.c
+++ b/memory.c
@@ -678,31 +678,23 @@ static void address_space_up
This way the accelerator (kvm) can handle them directly.
Signed-off-by: Avi Kivity
---
hw/vhost.c | 14 ++
kvm-all.c | 78
memory.c | 74 ++---
memory.h |4 +++
memory_region_set_offset() complicates the API, and has been deprecated
since its introduction. Now that it is no longer used, remove it.
Signed-off-by: Avi Kivity
---
memory.c | 26 ++
memory.h |9 -
2 files changed, 10 insertions(+), 25 deletions(-)
diff
This allows reverse iteration, which in turns allows consistent ordering
among multiple listeners:
l1->add
l2->add
l2->del
l1->del
Signed-off-by: Avi Kivity
---
hw/vhost.c |1 +
kvm-all.c |1 +
memory.c | 70 ++--
memo
So it can be used in earlier code.
Signed-off-by: Avi Kivity
---
memory.c | 64 +++---
1 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/memory.c b/memory.c
index cb2b4f1..a1013bc 100644
--- a/memory.c
+++ b/memory.c
@@ -82
On Wed, Feb 01, 2012 at 03:46:52PM +1100, David Gibson wrote:
> In order to safely drive a device with a userspace driver, or to pass
> it through to a guest system, we must first make sure that the device
> is isolated in such a way that it cannot interfere with other devices
> on the system. Thi
On 02/08/2012 09:04 AM, malc wrote:
On Wed, 8 Feb 2012, Andreas F?rber wrote:
malc,
Arbitrarily reformatting your files is not okay. If you want a different
formatting, you need to fix checkpatch.pl first to not error on that
formatting in your files.
It was always formatter like this (inter
On 02/08/12 01:17, Rusty Russell wrote:
> As featured on:
> https://bugs.launchpad.net/qemu-linaro/+bug/928432
>
> Since we compile with -Werror, the presence of spice headers breaks
> compile. Yet except for x86-64, it doesn't compile, doesn't work, isn't
> supported. See: http://spice-
So here are some of the problems im trying to solve with the bootloader:
Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
assumed to be not kernels).
Change the kernel, initrd and dtb load address on the command line.
Use my own SMP secondary bootloop.
My intention with t
On Wed, Feb 8, 2012 at 2:55 PM, Paolo Bonzini wrote:
> On 02/08/2012 03:39 PM, Stefan Hajnoczi wrote:
>>
>>
>>> > What about taking the existing Ceph/RBD driver in QEMU and changing it
>>> > to
>>> > support arbitrary image formats rather than just raw? That sounds
>>> > much much
>>> > easier
On Wed, 8 Feb 2012, Andreas F?rber wrote:
> malc,
>
> Arbitrarily reformatting your files is not okay. If you want a different
> formatting, you need to fix checkpatch.pl first to not error on that
> formatting in your files.
It was always formatter like this (internally consistent), then others
Am 01.02.2012 04:06, schrieb Supriya Kannery:
> Struct BDRVReopenState along with three reopen related functions
> introduced for handling reopening of images safely. This can be
> extended by each of the block drivers to reopen respective
> image files.
>
> Signed-off-by: Supriya Kannery
>
> In
1 - 100 of 181 matches
Mail list logo
