On Thu, Mar 07, 2013 at 02:41:26AM -0500, Paolo Bonzini wrote:
>
> > From Makefile.target, qtest is built when you build softmmu target.
> > I guess there is no need to add "--enable-qtest" option. However, I
> > don't know how to run qtest...
>
> make check-qtest-arm
O.K., let me try to sum
On 03/06/2013 11:05 PM, Eric Blake wrote:
On 03/06/2013 06:45 AM, Lei Li wrote:
Signed-off-by: Lei Li
---
qga/commands-win32.c | 35 +++
1 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 4febec7
2013/3/7 Paolo Bonzini :
>
>> From Makefile.target, qtest is built when you build softmmu target.
>> I guess there is no need to add "--enable-qtest" option. However, I
>> don't know how to run qtest...
>
> make check-qtest-arm
>
> Paolo
Got it, thanks.
--
Best wishes,
Kuo-Jung Su
Il 12/12/2012 22:36, Marcelo Tosatti ha scritto:
>
> RTC interrupt reinjection has no known negative effect. Lack of
> RTC interrupt reinjection, though, has negative effects: time drift
> for Windows guests which use it as a timer source.
>
> Based on that, enable lost_tick_policy=slew option as
This series tries to let guest instead of qemu to send the gratuitous packets
after migration when guest is capable of doing this. This is needed since it's
impossible for qemu to keep track of all configurations (e.g 802.1Q) and mac
addresses (more than one mac address may be used by guest). So qe
Sometimes, we need track the state when guest is just about to start after
migration. There's not a accurate state available which do this accurately
(consider qemu may started with -S in destination).
So this patch introduces a new state prelaunch-migrate which just tracks this
state, it covers t
Since we may want to send garp by guest if guest driver is capable of it. We
need trigger this event after vm is started. So this patch do this when the
state is changing from RUN_STATE_PRELAUNCH_MIGRATE to RUN_STATE_RUNINNG.
Signed-off-by: Jason Wang
---
migration.c |1 -
vl.c|4
It's hard to track all mac addresses and their configurations (e.g vlan) in
qemu. Without those information, it's impossible to build proper garp packet
after migration. The only possible solution to this is let guest ( who knew all
configurations) to do this.
So, this patch introduces a new rw co
This patch introduces a function pointer in NetClientInfo which is called during
self announcement. With this, each kind of card can announce the link with a
model specific way. The old method is still kept for cards that have not
implemented this or old guest. The first user would be virtio-net.
Disable guest announce for pre-1.5.
Signed-off-by: Jason Wang
---
hw/pc.h |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/hw/pc.h b/hw/pc.h
index f2c1b1c..2de7cd4 100644
--- a/hw/pc.h
+++ b/hw/pc.h
@@ -221,6 +221,10 @@ int e820_add_entry(uint64_t, uint64_t, uint32_t
On Thu, Mar 07, 2013 at 12:11:51PM +1000, Peter Crosthwaite wrote:
> Hi Kuo Jung, Peter,
>
> This patch fixes bugs for us in Zynq Nand (cc Wendy Liang). Can we get
> a cherry pick of this?
I've applied this one.
Thanks,
Edgar
>
> Regards,
> Peter
>
> On Wed, Mar 6, 2013 at 5:27 PM, Kuo-Jung
On Wed, Mar 06, 2013 at 07:53:51PM -0500, Kevin O'Connor wrote:
> On Thu, Mar 07, 2013 at 12:12:08AM +0100, Aurelien Jarno wrote:
> > On Wed, Mar 06, 2013 at 08:21:11AM +, Dietmar Maurer wrote:
> > > Using qemu 1.4.0:
> > >
> > > # qemu -hda test.raw -m 512 -cdrom
> > > pfSense-LiveCD-2.0.2-R
Peter Maydell writes:
> On 5 March 2013 04:16, Paolo Bonzini wrote:
>> Il 04/03/2013 18:58, Peter Maydell ha scritto:
> Mass-mark these devices as no_user.
>>> "There is no such thing as a 'no-user' device" -- Anthony
>>> (http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg00896.html)
Am 06.03.2013 um 21:39 hat Paolo Bonzini geschrieben:
> Il 06/03/2013 20:03, Peter Lieven ha scritto:
> > Am 06.03.2013 19:48, schrieb Jeff Cody:
> >> On Wed, Mar 06, 2013 at 07:31:51PM +0100, Paolo Bonzini wrote:
> >>> Il 06/03/2013 19:14, Jeff Cody ha scritto:
> QCOW breaks with it using a n
On 06.03.2013 21:39, Paolo Bonzini wrote:
Il 06/03/2013 20:03, Peter Lieven ha scritto:
Am 06.03.2013 19:48, schrieb Jeff Cody:
On Wed, Mar 06, 2013 at 07:31:51PM +0100, Paolo Bonzini wrote:
Il 06/03/2013 19:14, Jeff Cody ha scritto:
QCOW breaks with it using a normal raw posix file as a devi
On 07.03.2013 09:50, Kevin Wolf wrote:
Am 06.03.2013 um 21:39 hat Paolo Bonzini geschrieben:
Il 06/03/2013 20:03, Peter Lieven ha scritto:
Am 06.03.2013 19:48, schrieb Jeff Cody:
On Wed, Mar 06, 2013 at 07:31:51PM +0100, Paolo Bonzini wrote:
Il 06/03/2013 19:14, Jeff Cody ha scritto:
QCOW br
Am 06.03.2013 um 19:27 hat Peter Lieven geschrieben:
> Am 06.03.2013 19:06, schrieb Paolo Bonzini:
> > Il 06/03/2013 18:50, Peter Lieven ha scritto:
> Commit 9a665b2b made bdrv_truncate() call bdrv_drain_all(), but this
> breaks
> QCOW images, as well other future image formats (suc
Am 07.03.2013 um 09:53 hat Peter Lieven geschrieben:
> On 06.03.2013 21:39, Paolo Bonzini wrote:
> >Il 06/03/2013 20:03, Peter Lieven ha scritto:
> >>Am 06.03.2013 19:48, schrieb Jeff Cody:
> >>>On Wed, Mar 06, 2013 at 07:31:51PM +0100, Paolo Bonzini wrote:
> Il 06/03/2013 19:14, Jeff Cody ha s
Am 07.03.2013 um 09:56 hat Peter Lieven geschrieben:
> On 07.03.2013 09:50, Kevin Wolf wrote:
> >Am 06.03.2013 um 21:39 hat Paolo Bonzini geschrieben:
> >>Il 06/03/2013 20:03, Peter Lieven ha scritto:
> >>>Am 06.03.2013 19:48, schrieb Jeff Cody:
> On Wed, Mar 06, 2013 at 07:31:51PM +0100, Paolo
Am 06.03.2013 um 18:39 hat Dietmar Maurer geschrieben:
> > > > How about variable block sizes? I mean this is a stream format that
> > > > has a header for each block anyway. Include a size there and be done.
> > >
> > > You can make that as complex as you want. I simply do not need that.
> >
> >
On Wed, Mar 06, 2013 at 02:42:57PM +, Dietmar Maurer wrote:
> > > > Maybe you'd better use a different output format that doesn't
> > > > restrict you to 64k writes.
> > >
> > > The output format is not really the restriction. The problem is that
> > > an additional IPC layer add overhead, an d
Copying qemu-trivial.
Lei Li writes:
> Fix LP#1151450 the wrong description in qemu manual:
>
> 'qemu-system-x86_84' should be 'qemu-system-x86_64'.
>
> Signed-off-by: Lei Li
> ---
> qemu-options.hx |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/qemu-options.hx
On Thu, Mar 07, 2013 at 12:32:08AM -0600, Doug Goldstein wrote:
> The goal is to support an 'includedir' to include all files within a
> directory specified in the bridge.conf file. The rationale is to allow
> libvirt to be able to configure interfaces to for use by unprivileged
> users by just sim
Am 07.03.2013 um 10:03 schrieb Kevin Wolf :
> Am 07.03.2013 um 09:56 hat Peter Lieven geschrieben:
>> On 07.03.2013 09:50, Kevin Wolf wrote:
>>> Am 06.03.2013 um 21:39 hat Paolo Bonzini geschrieben:
Il 06/03/2013 20:03, Peter Lieven ha scritto:
> Am 06.03.2013 19:48, schrieb Jeff Cody:
>
Am 07.03.2013 um 10:16 hat Peter Lieven geschrieben:
> >> If bs->growable is 1 for all drivers, whats the fix status of
> >> CVE-2008-0928? This
> >> flag was introduced as a fix for this problem.
> >>
> >> bdrv_check_byte_request() does nothing useful if bs->growable is 1.
> >
> > Don't ignore
> > > > You can make that as complex as you want. I simply do not need that.
> > >
> > > Then you also don't need the performance that you lose by using NBD.
> >
> > Why exactly?
>
> Because your format kills more performance than any NBD connection could.
That is not true.
Am 07.03.2013 um 10:22 schrieb Kevin Wolf :
> Am 07.03.2013 um 10:16 hat Peter Lieven geschrieben:
If bs->growable is 1 for all drivers, whats the fix status of
CVE-2008-0928? This
flag was introduced as a fix for this problem.
bdrv_check_byte_request() does nothing use
> > When we run backup, we need to read such block on every write from the
> guest.
> > So if we increase block size we get additional delays.
>
> Don't increase the bitmap block size.
>
> Just let the block job do larger reads. This is the bulk of the I/O
> workload. You
> can use large reads
On Thu, Mar 07, 2013 at 10:06:52AM +0800, liu ping fan wrote:
> On Wed, Mar 6, 2013 at 5:30 AM, mdroth wrote:
> > On Sun, Mar 03, 2013 at 09:21:19PM +0800, Liu Ping Fan wrote:
> >> From: Liu Ping Fan
> >>
> >> This series aim to make netlayer re-entrant, so netlayer can
> >> run out of biglock sa
On Thu, Mar 07, 2013 at 10:06:52AM +0800, liu ping fan wrote:
> On Wed, Mar 6, 2013 at 5:30 AM, mdroth wrote:
> > On Sun, Mar 03, 2013 at 09:21:19PM +0800, Liu Ping Fan wrote:
> >> From: Liu Ping Fan
> >>
> >> This series aim to make netlayer re-entrant, so netlayer can
> >> run out of biglock sa
On Wed, Mar 06, 2013 at 02:15:25PM +0100, Samuel Thibault wrote:
> Stefan Hajnoczi, le Wed 06 Mar 2013 13:29:37 +0100, a écrit :
> > On Tue, Mar 05, 2013 at 05:35:10PM +0100, Samuel Thibault wrote:
> > Unfortunately net/socket.c does not have the concept of a link-layer
> > address, so we cannot ea
Eric Blake writes:
> [adding libvirt]
>
> On 03/06/2013 07:52 AM, Paolo Bonzini wrote:
>> Il 06/03/2013 15:44, Eric Blake ha scritto:
>>> Question - if libvirt misses the event (for example, if libvirtd
>>> requests a remove, but then gets restarted, and the event arrives before
>>> libvirtd is b
Public bug reported:
Description:
man qemu, there is a line:
qemu-system-x86_84 --drive file=gluster://192.0.2.1/testvol/a.img
seems should be:
qemu-system-x86_64 --drive file=gluster://192.0.2.1/testvol/a.img
Additional info:
* operating system
arch linux x86_64
* package version(s)
1.4.0
* con
On Thu, Mar 07, 2013 at 03:50:26PM +0800, Lei Li wrote:
> Fix LP#1151450 the wrong description in qemu manual:
>
> 'qemu-system-x86_84' should be 'qemu-system-x86_64'.
>
> Signed-off-by: Lei Li
> ---
> qemu-options.hx |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks, applie
libvirt has a long-standing bug: when removing the device,
it can request removal but does not know when the
removal completes. Add an event so we can fix this in a robust way.
Signed-off-by: Michael S. Tsirkin
---
Changes from v2:
- move event toward the end of device_unparent,
so tha
"Michael S. Tsirkin" writes:
> On Wed, Mar 06, 2013 at 02:57:22PM +0100, Andreas Färber wrote:
>> Am 06.03.2013 14:00, schrieb Michael S. Tsirkin:
>> > libvirt has a long-standing bug: when removing the device,
>> > it can request removal but does not know when does the
>> > removal complete. Add
On Thu, Mar 07, 2013 at 02:49:30PM +0800, yue-kvm wrote:
> i create qcow2 format image with -o encryption, and assign password.
>
> but when i qemu-img info encryt.qcow2 , it display encryt.qcow2 info no
> master what i input, even just hit enter.
> the 'Password Authentication ' of qemu-img ma
Am 07.03.2013 um 10:25 hat Peter Lieven geschrieben:
>
> Am 07.03.2013 um 10:22 schrieb Kevin Wolf :
>
> > Am 07.03.2013 um 10:16 hat Peter Lieven geschrieben:
> If bs->growable is 1 for all drivers, whats the fix status of
> CVE-2008-0928? This
> flag was introduced as a fix for
On 7 March 2013 16:48, Markus Armbruster wrote:
> Can we make some progress towards something that makes more sense?
>
> First step: reasons for marking a device no_user.
>
> From a user point of view, I think there's just one: -device/device_add
> cannot possibly result in a working device. Cohe
On Wed, Mar 06, 2013 at 06:24:37PM +0100, Paolo Bonzini wrote:
> Il 06/03/2013 16:45, Stefan Hajnoczi ha scritto:
> > This patch adds a ThreadPool to AioContext. It's possible that some
> > AioContext instances will never use the ThreadPool, so defer creation
> > until aio_get_thread_pool().
>
>
On Thu, Mar 07, 2013 at 04:23:46PM +0800, Jason Wang wrote:
> This series tries to let guest instead of qemu to send the gratuitous packets
> after migration when guest is capable of doing this. This is needed since it's
> impossible for qemu to keep track of all configurations (e.g 802.1Q) and mac
On Thu, Mar 07, 2013 at 10:55:23AM +0100, Markus Armbruster wrote:
> "Michael S. Tsirkin" writes:
>
> > On Wed, Mar 06, 2013 at 02:57:22PM +0100, Andreas Färber wrote:
> >> Am 06.03.2013 14:00, schrieb Michael S. Tsirkin:
> >> > libvirt has a long-standing bug: when removing the device,
> >> > it
On Wed, Mar 06, 2013 at 05:35:09PM +0100, Paolo Bonzini wrote:
> Il 06/03/2013 16:45, Stefan Hajnoczi ha scritto:
> > Now that each AioContext has a ThreadPool and the main loop AioContext
> > can be fetched with qemu_get_aio_context(), we can eliminate the concept
> > of a global thread pool from
On Wed, Mar 06, 2013 at 04:03:49PM +0100, Paolo Bonzini wrote:
> Il 06/03/2013 15:53, Stefan Hajnoczi ha scritto:
> > CoQueue uses a BH to awake coroutines that were made ready to run again
> > using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
> > currently runs in the iothread Aio
On 03/07/2013 06:04 PM, Michael S. Tsirkin wrote:
> On Thu, Mar 07, 2013 at 04:23:46PM +0800, Jason Wang wrote:
>> This series tries to let guest instead of qemu to send the gratuitous packets
>> after migration when guest is capable of doing this. This is needed since
>> it's
>> impossible for qe
From: Riku Voipio
Hi,
I did a dig through the archive for linux-user patches
that have slipped through during my inactivity. The ones
in this patchset appear good and pass smoketest.
I will send these as pull request once I'm back from travel
and can update my git repository.
Riku
Dillon Amb
From: Dillon Amburgey
Without these, some networking programs will not work
Signed-off-by: Dillon Amburgey
Reviewed-by: Richard Henderson
Signed-off-by: Riku Voipio
---
linux-user/socket.h | 69 +
1 file changed, 69 insertions(+)
diff --gi
From: John Rigby
Handle same as existing FUTEX_PRIVATE_FLAG.
Signed-off-by: John Rigby
Signed-off-by: Riku Voipio
---
linux-user/strace.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/linux-user/strace.c b/linux-user/strace.c
index 9a18146..0fbae3c 100644
--- a/linux-user/strace.c
From: Laurent Vivier
Signed-off-by: Laurent Vivier
Signed-off-by: Riku Voipio
---
linux-user/strace.c | 97 +++--
1 file changed, 79 insertions(+), 18 deletions(-)
diff --git a/linux-user/strace.c b/linux-user/strace.c
index 4e91a6e..9a18146 100
From: Laurent Vivier
The parameter "union semun" of semctl() is not a value
but a pointer to the value.
Moreover, all fields of target_su must be swapped (if needed).
The third argument of shmctl is a pointer.
WITHOUT this patch:
$ ipcs
kernel not configured for shared memory
qemu: uncaught
From: Dillon Amburgey
Signed-off-by: Dillon Amburgey
Reviewed-by: Peter Maydell
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 7f12563..e0c71fb 1
From: John Rigby
Upstream libc has recently changed to start using
FUTEX_WAIT_BITSET instead of FUTEX_WAIT and this
is causing do_futex to return -TARGET_ENOSYS.
Pass bitset in val3 to sys_futex which will be
ignored by kernel for the FUTEX_WAIT case.
Signed-off-by: John Rigby
Signed-off-by: R
From: Dillon Amburgey
Signed-off-by: Dillon Amburgey
Signed-off-by: Riku Voipio
---
linux-user/sparc/syscall_nr.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/linux-user/sparc/syscall_nr.h b/linux-user/sparc/syscall_nr.h
index 061711c..534e6e9 100644
--- a/linux-user/sparc/syscall_nr.
On Thu, Mar 07, 2013 at 06:13:41PM +0800, Jason Wang wrote:
> On 03/07/2013 06:04 PM, Michael S. Tsirkin wrote:
> > On Thu, Mar 07, 2013 at 04:23:46PM +0800, Jason Wang wrote:
> >> This series tries to let guest instead of qemu to send the gratuitous
> >> packets
> >> after migration when guest is
On Wed, Mar 06, 2013 at 04:41:01PM +0100, Kevin Wolf wrote:
> Am 06.03.2013 um 15:53 hat Stefan Hajnoczi geschrieben:
> > CoQueue uses a BH to awake coroutines that were made ready to run again
> > using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
> > currently runs in the iothread
Am 07.03.2013 um 11:00 schrieb Kevin Wolf :
> Am 07.03.2013 um 10:25 hat Peter Lieven geschrieben:
>>
>> Am 07.03.2013 um 10:22 schrieb Kevin Wolf :
>>
>>> Am 07.03.2013 um 10:16 hat Peter Lieven geschrieben:
>> If bs->growable is 1 for all drivers, whats the fix status of
>> CVE-2008-
On 03/07/2013 06:25 PM, Michael S. Tsirkin wrote:
> On Thu, Mar 07, 2013 at 06:13:41PM +0800, Jason Wang wrote:
>> On 03/07/2013 06:04 PM, Michael S. Tsirkin wrote:
>>> On Thu, Mar 07, 2013 at 04:23:46PM +0800, Jason Wang wrote:
This series tries to let guest instead of qemu to send the gratui
On 28.02.2013, at 10:39, Jens Freimann wrote:
> From: Ekaterina Tumanova
>
> dump-guest-memory QEMU monitor command didn't work for s390 architecture.
> The result of the command is supposed to be ELF format crash-readable
> dump.
> In order to implement this, the arch-specific part of dump-gue
On Thu, Mar 07, 2013 at 06:33:30PM +0800, Jason Wang wrote:
> On 03/07/2013 06:25 PM, Michael S. Tsirkin wrote:
> > On Thu, Mar 07, 2013 at 06:13:41PM +0800, Jason Wang wrote:
> >> On 03/07/2013 06:04 PM, Michael S. Tsirkin wrote:
> >>> On Thu, Mar 07, 2013 at 04:23:46PM +0800, Jason Wang wrote:
>
hi stefan:
[root@kvm ~]# qemu-img -V
qemu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellard
OS centos 6.3
thanks
At 2013-03-07 17:56:50,"Stefan Hajnoczi" wrote:
>On Thu, Mar 07, 2013 at 02:49:30PM +0800, yue-kvm wrote:
>> i create qcow2 format image with -o encryption, and as
On Thu, Mar 07, 2013 at 06:57:19PM +0800, yue-kvm wrote:
> hi stefan:
>
> [root@kvm ~]# qemu-img -V
> qemu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellard
Hrm..., 0.12 is too old, why don't you use newer version?
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institu
On Wed, Feb 8, 2012 at 10:46 AM, Laurent Desnogues
wrote:
> On Fri, Feb 3, 2012 at 3:49 PM, wrote:
>> From: Riku Voipio
>>
>> Signed-off-by: Riku Voipio
>> ---
>> linux-user/qemu.h |2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/linux-user/qemu.h b/linux-user
Hi,
> Probably works, but never appeared in a separate release:
>
> commit 3588185b8396eb97fd9efd41c2b97775465f67c4
> Author: Gerd Hoffmann
> Date: Mon Jan 21 09:17:16 2013 +0100
>
> seabios: update to 1.7.2 release
Built with "gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
Ping!
Any issues here? Peter wanted to give this list time so it missed the
last arm-devs.
Regards,
Peter
On Wed, Feb 27, 2013 at 3:17 PM, Peter Crosthwaite
wrote:
> Factor out the hexdumper functionality from iov for all to use. Useful for
> creating verbose debug printfery that dumps packet d
On 07/03/13 11:49, Alexander Graf wrote:
>
> On 28.02.2013, at 10:39, Jens Freimann wrote:
>
>> From: Ekaterina Tumanova
>>
>> dump-guest-memory QEMU monitor command didn't work for s390 architecture.
>> The result of the command is supposed to be ELF format crash-readable
>> dump.
>> In order t
On 07.03.2013, at 12:21, Christian Borntraeger wrote:
> On 07/03/13 11:49, Alexander Graf wrote:
>>
>> On 28.02.2013, at 10:39, Jens Freimann wrote:
>>
>>> From: Ekaterina Tumanova
>>>
>>> dump-guest-memory QEMU monitor command didn't work for s390 architecture.
>>> The result of the command
diff --git a/target-s390x/arch_memory_mapping.c
b/target-s390x/arch_memory_mapping.c
new file mode 100644
index 000..3dad3b9
--- /dev/null
+++ b/target-s390x/arch_memory_mapping.c
@@ -0,0 +1,26 @@
+/*
+ * s390x memory mapping
+ *
+ * Copyr
On 07.03.2013, at 12:30, Christian Borntraeger wrote:
> diff --git a/target-s390x/arch_memory_mapping.c
> b/target-s390x/arch_memory_mapping.c
> new file mode 100644
> index 000..3dad3b9
> --- /dev/null
> +++ b/target-s390x/arch_memory_mapping.c
> @@ -0,0 +1,26 @@
Hi,
>> Would qemu consider using those blobs rather than different developers
>> using their distro toolchain to build up a random commit ID. I say
>> random only because often qemu releases ship with a non-release
>> seabios.
It happened (well, the snapshot thing). But that isn't our preferre
On 03/07/13 09:43, Aurelien Jarno wrote:
> I did a git bisect to find the commit fixing the issue. Then, as I was
> not believing the result, I tried the following sequence a dozen of
> times (for some unknown reasons the FreeBSD install CD doesn't exhibit
> the issue, so I used the Debian GNU/kFr
Ping.
Anthony, Jesse,
how is this supposed to work?
Christian
On 05/03/13 18:03, Christian Borntraeger wrote:
> On 05/03/13 17:48, Alexander Graf wrote:
>> On 02/06/2013 12:47 AM, Jesse Larrew wrote:
>>> Currently, the config size for virtio devices is hard coded. When a new
>>> feature is added
On 03/06/2013 10:52 PM, Peter Maydell wrote:
On 7 March 2013 02:31, Michael Walle
wrote:
Sorry for digging out such an old thread :) but this patch introduced a memory
corruption, see below.
CC'ing Igor as the author of the patch...
Am Dienstag 30 Oktober 2012, 09:44:24 schrieb Peter May
Peter Maydell writes:
> On 7 March 2013 16:48, Markus Armbruster wrote:
>> Can we make some progress towards something that makes more sense?
>>
>> First step: reasons for marking a device no_user.
>>
>> From a user point of view, I think there's just one: -device/device_add
>> cannot possibly r
This patch series changes the global thread pool to a one ThreadPool per
AioContext model. We still only use the main loop AioContext so in practice
there is just one ThreadPool. But this opens the door to refactoring the block
layer (which depends on ThreadPool) so block devices can be accessed
It is very useful to get the main loop AioContext, which is a static
variable in main-loop.c.
I'm not sure whether qemu_get_aio_context() will be necessary in the
future once devices focus on using their own AioContext instead of the
main loop AioContext, but for now it allows us to refactor code
Move global variables into a struct so multiple thread pools can be
supported in the future.
This patch does not change thread-pool.h interfaces. There is still a
global thread pool and it is not yet possible to create/destroy
individual thread pools. Moving the variables into a struct first mak
For now bdrv_get_aio_context() is just a stub that calls
qemu_aio_get_context() since the block layer is currently tied to the
main loop AioContext.
Add the stub now so that the block layer can begin accessing its
AioContext.
Signed-off-by: Stefan Hajnoczi
---
block.c | 6
ThreadPool is tied to an AioContext through its event notifier, which
dictates in which AioContext the work item's callback function will be
invoked.
In order to support multiple AioContexts we need to support multiple
ThreadPool instances.
This patch adds the new/free functions. The free functi
Now that each AioContext has a ThreadPool and the main loop AioContext
can be fetched with bdrv_get_aio_context(), we can eliminate the concept
of a global thread pool from thread-pool.c.
The submit functions must take a ThreadPool* argument.
block/raw-posix.c and block/raw-win32.c use
aio_get_th
Hi Peter,
[snip]
> Case four: "we really don't expect anybody to be trying to wire this
> up dynamically", which would apply to things like the on-cpu peripherals
> for some ARM cores.
What ARM cores were you thinking here exactly? We are already doing
dynamic machine creation of ARM systems incl
This patch adds a ThreadPool to AioContext. It's possible that some
AioContext instances will never use the ThreadPool, so defer creation
until aio_get_thread_pool().
The reason why AioContext should have the ThreadPool is because the
ThreadPool is bound to a AioContext instance where the work it
CoQueue uses a BH to awake coroutines that were made ready to run again
using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
currently runs in the iothread AioContext and would break coroutines
that run in a different AioContext.
This is a slightly tricky problem because the lifetime
Am 06.03.2013 08:21, schrieb Dmitry Fleytman:
> Signed-off-by: Dmitry Fleytman
> Signed-off-by: Yan Vugenfirer
> ---
> default-configs/pci.mak |1 +
> hw/Makefile.objs|1 +
> hw/pci/pci.h|1 +
> hw/vmxnet3.c| 2460
> +++
Am 07.03.2013 10:49, schrieb Michael S. Tsirkin:
> libvirt has a long-standing bug: when removing the device,
> it can request removal but does not know when the
> removal completes. Add an event so we can fix this in a robust way.
>
> Signed-off-by: Michael S. Tsirkin
> ---
>
> Changes from v2:
07.03.2013 15:56, Gerd Hoffmann wrote:
>> Just a note, or an "alternative opinion", so to say. In Debian, we have
>> a social contract which, among other things, ensures that the binaries
>> you, as a user, get, comes with source which you can modify on the
>> system you installed. This requires
Am 07.03.2013 11:07, schrieb Michael S. Tsirkin:
> On Thu, Mar 07, 2013 at 10:55:23AM +0100, Markus Armbruster wrote:
>> "Michael S. Tsirkin" writes:
>>
>>> On Wed, Mar 06, 2013 at 02:57:22PM +0100, Andreas Färber wrote:
Am 06.03.2013 14:00, schrieb Michael S. Tsirkin:
> libvirt has a lon
Juan Quintela writes:
> v2:
> Add Markus sugestions:
This needs to go below the --- line.
> Signed-off-by: Juan Quintela
> ---
> qmp-commands.hx | 50 ++
> 1 file changed, 30 insertions(+), 20 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-
Move RAM migration code from arch_init to savevm-ram.
Signed-off-by: Michael S. Tsirkin
---
Note: this is on top of Juan's pull request
Changes from v1:
- renamed source file, rebased on top of migration.next as
suggested by Paolo
Makefile.target | 2 +-
arch_init.c | 763
On Wed, Mar 06, 2013 at 09:47:41AM -0500, Jeff Cody wrote:
> +#define VHDX_ZERO_MGIC 0x6F72657A /* 'zero' */
s/MGIC/MAGIC/
> +typedef struct QEMU_PACKED vhdx_log_zero_descriptor {
> +uint32_tzero_signature; /* "zero" in ASCII */
> +uint32_treserver;
s/reserver/reserved/ ?
于 2013-3-7 11:40, li guang 写道:
Hi, Anthony and all
By now all devices of QEMU do not have much more
power management consideration, for example, if
system do suspend, it will call all registered notifiers,
this was loosely required, and the code to do power management
state transition seems just
On Thu, Mar 07, 2013 at 02:15:42PM +0100, Stefan Hajnoczi wrote:
> On Wed, Mar 06, 2013 at 09:47:41AM -0500, Jeff Cody wrote:
> > +#define VHDX_ZERO_MGIC 0x6F72657A /* 'zero' */
>
> s/MGIC/MAGIC/
>
> > +typedef struct QEMU_PACKED vhdx_log_zero_descriptor {
> > +uint32_tzero_signature;
Thanks, Andreas
Now I see.
We'll resubmit our patches soon.
Dmitry.
On Thu, Mar 7, 2013 at 2:59 PM, Andreas Färber wrote:
> Am 06.03.2013 08:21, schrieb Dmitry Fleytman:
> > Signed-off-by: Dmitry Fleytman
> > Signed-off-by: Yan Vugenfirer
> > ---
> > default-configs/pci.mak |1 +
> > h
On Thu, Mar 07, 2013 at 01:16:54PM +0100, Laszlo Ersek wrote:
> On 03/07/13 09:43, Aurelien Jarno wrote:
>
> > I did a git bisect to find the commit fixing the issue. Then, as I was
> > not believing the result, I tried the following sequence a dozen of
> > times (for some unknown reasons the Free
Am 25.02.2013 02:03, schrieb Igor Mammedov:
> Signed-off-by: Igor Mammedov
I vaguely remember having written something like this long time ago for
ISA and for Vasilis... looks good except for minor nits.
> ---
> hw/qdev-properties.c | 33 +
> hw/qdev-properties
On Thu, Mar 07, 2013 at 09:43:04AM +0100, Aurelien Jarno wrote:
> On Wed, Mar 06, 2013 at 07:53:51PM -0500, Kevin O'Connor wrote:
> > That change is definitely just build related - I don't see how it
> > could impact the final SeaBIOS binary. How did you conclude that this
> > commit is what fixes
Andreas Färber writes:
> Am 07.03.2013 11:07, schrieb Michael S. Tsirkin:
>> On Thu, Mar 07, 2013 at 10:55:23AM +0100, Markus Armbruster wrote:
>>> "Michael S. Tsirkin" writes:
>>>
On Wed, Mar 06, 2013 at 02:57:22PM +0100, Andreas Färber wrote:
> Am 06.03.2013 14:00, schrieb Michael S.
Gerd Hoffmann writes:
> Add a linked list of keyboard handlers. Added handlers will go
> to the head of the list. Removed handlers will be zapped from
> the list. The head of the list will be used for events.
>
> This fixes the keyboard-dead-after-usb-kbd-unplug issue, key events
> will be re-
Gerd Hoffmann writes:
> There is no need for anybody outside ui/input.c to access the
> struct elements. Move the definitions, leaving only the typedefs
> in the header files.
No-brainer (assuming it compiles).
Reviewed-by: Markus Armbruster
On Wed, Mar 06, 2013 at 09:48:11AM -0500, Jeff Cody wrote:
> +#define leguid_to_cpus(guid) do { \
> +le32_to_cpus(&(guid)->data1); \
> +le16_to_cpus(&(guid)->data2); \
> +le16_to_cpus(&(guid)->data3); } while (0)
This should be a function. Please avoid macros.
> +static const ms_guid
Hi all,
recently I've tried to teach megasas MSI/MSI-X. While it works
perfectly under Linux, Windows refuses to.
With really strange symptoms:
Windows Vista will BSOD when both MSI/MSI-X registers are present,
and Windows 7 will hang as Windows (apparently) thinks MSI/MSI-X is
enabled, wher
1 - 100 of 197 matches
Mail list logo
