On 12/08/2011 04:48 AM, Michael Roth wrote:
This patch fixes a bug where child processes of launch_script() can
misbehave due to SIGCHLD being blocked. In the case of `sudo`, this
causes a permanent hang.
Previously a SIGCHLD handler was added to reap fork_exec()'d zombie
processes by calling wa
On 12/05/11 05:29, Alexey Korolev wrote:
> Hi Gerd,
>
> We have very early prototype of data acquisition device, with quite
> large MMIO buffer. It is an emulated device.
> We are running the 0.15 release.
> 0.15 doesn't work correctly with 64bit BARs so I've already added some
> hacks to Seabios
Hi all,
As the subject says, this is an RFC.
I have a few patches (to follow), that change the help output from QEMU
so that we only display options that are accepted by the arch of the
running binary.
So for example qemu-system-ppc64 will not tell you about i386 options
like -no-acpi, -no-hpet
Cher(s) CLIENTS, cgp(s) indépendant(s), cabinet(s) de commercilisation,
promoteur(s)... Rendez-vous sur www.mes-contacts.com (recommandé par les
promoteurs) pour obtenir maintenant les meilleurs Contacts entrants en
Défiscalisation et Placements financiers (Ass.vie,
SCPI,mutuelle,retraite..)
Make it possible to specify what architecture a heading in the help
doco applies to.
Signed-off-by: Michael Ellerman
---
A possibly nicer way to do this would be to add a new macro, perhaps
ARCHHEADING, that is used for architecture specific headings. That
would make the help source nicer, in t
Only print options in the help output that are accepted by our arch.
Signed-off-by: Michael Ellerman
---
vl.c | 31 +--
1 files changed, 17 insertions(+), 14 deletions(-)
diff --git a/vl.c b/vl.c
index b492f8c..ba8e76d 100644
--- a/vl.c
+++ b/vl.c
@@ -1492,28 +1492
In help() we do what boils down to:
printf("%s", "qemu");
This seems to be an artifact of be995c27640a82c7056b6f53d02ec823570114e5
("removed unused code"), which removed some ifdef'ery that used to print
a different name depending on CONFIG_SOFTMMU.
But now that is gone and we always use "qemu
Hi,
> +} else if (descriptors[i + 5] != s->configuration) {
> +fprintf(stderr, "not requested configuration %d\n",
> +s->configuration);
> +i += (descriptors[i + 3] << 8) + descriptors[i + 2];
> +continue;
> +}
That message
Am 12.12.2011 09:21, schrieb Michael Ellerman:
> In help() we do what boils down to:
>
> printf("%s", "qemu");
>
> This seems to be an artifact of be995c27640a82c7056b6f53d02ec823570114e5
> ("removed unused code"), which removed some ifdef'ery that used to print
> a different name depending on
Am 11.12.2011 11:45, schrieb Alex Bligh:
>
>
> --On 8 December 2011 13:40:57 +0100 Kevin Wolf wrote:
>
>>> qemu-img convert appears to support block devices as input, but not
>>> as output. That is irritating, as when using qemu-img convert to
>>> convert qcow to raw on a block partition, an in
Am 12.12.2011 00:42, schrieb Paul Brook:
>> This series makes target-i386 compile with DEBUG_TCGV_TL.
>
> What benefit does this provide?
It showcases what changes would need to be done to allow type-safe
compilation of the first pair of --enable-system targets.
Especially my focus has been on h
On Fri, Dec 9, 2011 at 1:10 PM, Michael Niehren
<902...@bugs.launchpad.net> wrote:
> Strace on the hanging qemu-img ends on:
>
> select(5, [4], [], NULL, NULL) = 1 (in [4])
> read(4, "\0", 16) = 1
> close(3) = 0
> open("test.img", O_RDON
On 14 November 2011 17:21, andrzej zaborowski wrote:
> On 14 November 2011 09:08, Peter Maydell wrote:
>> I'm happy that non-rndis works, I tested that. What I don't know
>> is whether the patch breaks rndis
>
> Sorry, I misread what you said assuming that you tested a branch
> affected by this p
On Sun, Dec 11, 2011 at 10:29 AM, Alon Levy wrote:
> On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
>> Hi there,
>>
>> I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out that
>> the command client_migrate_info uses it. That's a legacy interface and has to
>>
--On 12 December 2011 10:48:43 +0100 Kevin Wolf wrote:
I was testing on:
amb@alex-test:~$ qemu-img --version
qemu-img version 0.12.3, Copyright (c) 2004-2008 Fabrice Bellard
That's the problem. It should work since 0.13.
Thanks
--
Alex Bligh
Am 12.12.2011 00:28, schrieb Paul Brook:
>>> What mismatches does this catch that the existing debug code doesn't?
>>
>> Cf. patch 4/4:
>>
>> TCGv tmp = tcg_temp_new_i32();
>> tcg_temp_free_i32(tmp);
>>
>> TCGv_i32 tmp2 = tcg_temp_new();
>> tcg_temp_free(tmp2);
>
> Why is this a problem? If TARGE
Blue Swirl wrote:
> Instead of each target knowing or guessing the guest page size,
> just pass the desired size of dirtied memory area. This should also
> improve performance due to memset() optimizations.
My understanding last time I looked at this, is that it is as easy
basically to change the
The following changes since commit f18318eef8b4b263f4e82a5338c9b2875a6c73c8:
Merge branch 'master' of git://git.qemu.org/qemu (2011-12-12 04:12:31 +0400)
are available in the git repository at:
git://git.linaro.org/people/pmaydell/qemu-arm.git arm-devs.for-upstream
Peter Chubb (1):
Fi
hw/mpcore.c is now implementing only ARM11MPCore specific peripherals,
and is #included only from hw/arm11mpcore.c, so just merge it into that
file.
Signed-off-by: Peter Maydell
---
hw/arm11mpcore.c | 130 ++-
hw/mpcore.c | 137 -
Turn the ARM MPcore private timer/watchdog blocks into separate
qdev devices. This will allow us to share them neatly between
11MPCore and A9MPcore.
Signed-off-by: Peter Maydell
---
Makefile.target |1 +
hw/arm_mptimer.c | 332 ++
hw/mpco
Add a .mailmap file so 'git shortlog' can map the unfriendly
pre-git-conversion author entries to real names.
Signed-off-by: Peter Maydell
---
v1->v2:
fixed Andrzej's email to match MAINTAINERS file
added entries for Fabrice Bellard, Jocelyn Mayer
cc'd active maintainers with an entry in the m
Switch to using the GIC memory regions for the CPU interface
rather than hand implementing them as a subcase of mpcore_priv_read()
and mpcore_priv_write().
Signed-off-by: Peter Maydell
---
hw/mpcore.c | 35 ++-
1 files changed, 10 insertions(+), 25 deletions(-)
Implement the A9MP private peripheral region correctly, rather
than piggybacking on the 11MPCore code; the two CPUs are not the
same in this area.
Signed-off-by: Peter Maydell
---
hw/a9mpcore.c | 189 ++---
1 files changed, 179 insertions(+),
On Mon, 2011-12-12 at 02:52 +, Paul Brook wrote:
> I've taken a look at the virtion-mmio spec, and it looks fairly
> reasonable.
>
> The only thing I'd change is the GuestPageSize/QueuePFN mess. Seems like
> just
> using straight 64-bit addresses would be a better solution. Maybe split int
The only code left in mpcore_priv_read and mpcore_priv_write is now
the implementation of the SCU registers. Clean up by renaming functions
and removing some unnecessary conditionals to make this clearer.
Signed-off-by: Peter Maydell
---
hw/mpcore.c | 73 +--
Use the GIC provided memory region for the CPU interface rather
than implementing our own.
Signed-off-by: Peter Maydell
---
hw/realview_gic.c | 25 +
1 files changed, 1 insertions(+), 24 deletions(-)
diff --git a/hw/realview_gic.c b/hw/realview_gic.c
index 479f939..8c4
Expose the ARM GIC CPU interfaces as memory regions, rather than
just providing read and write functions for them.
Signed-off-by: Peter Maydell
---
hw/arm_gic.c | 75 +-
1 files changed, 74 insertions(+), 1 deletions(-)
diff --git a/hw/a
On 12/12/11 11:18, Stefan Hajnoczi wrote:
> On Sun, Dec 11, 2011 at 10:29 AM, Alon Levy wrote:
>> On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
>>> Hi there,
>>>
>>> I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out
>>> that
>>> the command client_migrate
From: Peter Chubb
Properly implement dual-timer read/write for the sp804 dual timer module.
Based on ARM specs at
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0271d/index.html
Signed-off-by: Hans Jang
Signed-off-by: David Mirabito
Signed-off-by: Peter Chubb
Signed-off-by: Pe
Am 12.12.2011 06:54, schrieb Li Zhi Hui:
> v3: modify some errors
>
> Signed-off-by: Li Zhi Hui
> ---
> block/cow.c | 44 +---
> 1 files changed, 29 insertions(+), 15 deletions(-)
Thanks, applied to the block branch.
Kevin
On Fri, Dec 09, 2011 at 10:12:17PM +0530, M. Mohan Kumar wrote:
> On Friday, December 09, 2011 12:01:14 AM Stefan Hajnoczi wrote:
> > On Mon, Dec 05, 2011 at 09:48:41PM +0530, M. Mohan Kumar wrote:
> > > +static int read_request(int sockfd, struct iovec *iovec, ProxyHeader
> > > *header) +{
> > > +
On Mon, Dec 12, 2011 at 11:29 AM, Gerd Hoffmann wrote:
> On 12/12/11 11:18, Stefan Hajnoczi wrote:
>> On Sun, Dec 11, 2011 at 10:29 AM, Alon Levy wrote:
>>> On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
Hi there,
I'm about to completely drop the MONITOR_CMD_ASYNC
I noticed the virtio-mmio spec has an interrupt status register. On
x86 and virtio-pci things are moving towards Message Signalled
Interrupts and virtqueues having their own interrupts for better
performance and flexibility. Any thoughts on how 1 interrupt per
virtqueue works for virtio-mmio?
My
On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote:
> I noticed the virtio-mmio spec has an interrupt status register. On
> x86 and virtio-pci things are moving towards Message Signalled
> Interrupts and virtqueues having their own interrupts for better
> performance and flexibility. Any th
On 12/12/11 13:10, Stefan Hajnoczi wrote:
> On Mon, Dec 12, 2011 at 11:29 AM, Gerd Hoffmann wrote:
>> On 12/12/11 11:18, Stefan Hajnoczi wrote:
>>> On Sun, Dec 11, 2011 at 10:29 AM, Alon Levy wrote:
On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
> Hi there,
>
>
On Sun, 11 Dec 2011 12:00:12 +0200
Dor Laor wrote:
> On 12/08/2011 08:52 PM, Luiz Capitulino wrote:
> > This is basically suspend to disk on a Linux guest.
> >
> > Signed-off-by: Luiz Capitulino
> > ---
> >
> > This is an RFC because I did it as simple as possible and I'm open to
> > suggestions.
On Fri, 9 Dec 2011, Anthony PERARD wrote:
> This patch change the xen_map_cache behavior. Before trying to map a guest
> addr, mapcache will look into the list of range of address that have been
> moved
> (physmap/set_memory). There is currently one memory space like this, the vram,
> "moved" from
On Fri, 9 Dec 2011, Anthony PERARD wrote:
> Do not allocate RAM during pre-migration runstate.
> Do not actually "do" set_memory during migration.
>
> Signed-off-by: Anthony PERARD
> ---
> xen-all.c | 13 +
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/xen-a
On Fri, 9 Dec 2011, Anthony PERARD wrote:
> During the initialisation of the machine at restore time, the access to the
> VRAM will fail because QEMU does not know yet the right guest address to map,
> so the vram_ptr is NULL.
>
> So this patch avoid using a NULL pointer during initialisation, and
On Mon, Dec 12, 2011 at 12:28:27PM +, Pawel Moll wrote:
> On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote:
> > I noticed the virtio-mmio spec has an interrupt status register. On
> > x86 and virtio-pci things are moving towards Message Signalled
> > Interrupts and virtqueues having th
On Sat, 10 Dec 2011, Jan Kiszka wrote:
> On 2011-12-09 22:54, Anthony PERARD wrote:
> > During the initialisation of the machine at restore time, the access to the
> > VRAM will fail because QEMU does not know yet the right guest address to
> > map,
> > so the vram_ptr is NULL.
> >
> > So this pa
On Mon, 2011-12-12 at 13:12 +, Michael S. Tsirkin wrote:
> On Mon, Dec 12, 2011 at 12:28:27PM +, Pawel Moll wrote:
> > On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote:
> > > I noticed the virtio-mmio spec has an interrupt status register. On
> > > x86 and virtio-pci things are mov
On 2011-12-12 14:18, Stefano Stabellini wrote:
> On Sat, 10 Dec 2011, Jan Kiszka wrote:
>> On 2011-12-09 22:54, Anthony PERARD wrote:
>>> During the initialisation of the machine at restore time, the access to the
>>> VRAM will fail because QEMU does not know yet the right guest address to
>>> map
On Mon, 12 Dec 2011, Jan Kiszka wrote:
> On 2011-12-12 14:18, Stefano Stabellini wrote:
> > On Sat, 10 Dec 2011, Jan Kiszka wrote:
> >> On 2011-12-09 22:54, Anthony PERARD wrote:
> >>> During the initialisation of the machine at restore time, the access to
> >>> the
> >>> VRAM will fail because QE
> I can do that, but not this year (on holiday from Friday 16th, without
> any access to Internet whatsoever :-) One think to be decided is in what
> order the halfs should be filled? Low first, then high? High then low?
> Does it matter at all? :-)
My inital though was that you shouldn't be chang
On Mon, 2011-12-12 at 14:45 +, Paul Brook wrote:
> I suggest that the device to buffer writes to the high part, and construct
> the
> actual 64-bit value when the low part is written. That allows 32-bit guests
> can ignore the high part entirely.
This sounds good to me. If we define the re
> Am 12.12.2011 00:42, schrieb Paul Brook:
> >> This series makes target-i386 compile with DEBUG_TCGV_TL.
> >
> > What benefit does this provide?
>
> It showcases what changes would need to be done to allow type-safe
> compilation of the first pair of --enable-system targets.
How is the existing
On 2011-12-12 15:41, Stefano Stabellini wrote:
> On Mon, 12 Dec 2011, Jan Kiszka wrote:
>> On 2011-12-12 14:18, Stefano Stabellini wrote:
>>> On Sat, 10 Dec 2011, Jan Kiszka wrote:
On 2011-12-09 22:54, Anthony PERARD wrote:
> During the initialisation of the machine at restore time, the ac
On Mon, Dec 12, 2011 at 2:50 PM, takizo wrote:
>
> On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote:
>
>> On Sun, Dec 11, 2011 at 4:40 PM, takizo wrote:
>>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none
>>> /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp
>>> 1
On Mon, Dec 12, 2011 at 12:28 PM, Pawel Moll wrote:
> On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote:
>> I noticed the virtio-mmio spec has an interrupt status register. On
>> x86 and virtio-pci things are moving towards Message Signalled
>> Interrupts and virtqueues having their own in
On 12 December 2011 15:11, Stefan Hajnoczi wrote:
> If there aren't already then pretty soon ARM-based systems will deal
> with PCIe and Message Signalled Interrupts. Are you sure new ARM
> boards are constraints to a small number of physical interrupts?
Depends what you mean by "small number".
On Dec 12, 2011, at 11:08 PM, Stefan Hajnoczi wrote:
> On Mon, Dec 12, 2011 at 2:50 PM, takizo wrote:
>>
>> On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote:
>>
>>> On Sun, Dec 11, 2011 at 4:40 PM, takizo wrote:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none
/usr
On Mon, 2011-12-12 at 15:11 +, Stefan Hajnoczi wrote:
> If there aren't already then pretty soon ARM-based systems will deal
> with PCIe and Message Signalled Interrupts.
Actually PCI is not an alien in ARM world - we had platforms with PCI
long time ago. And new SOCs aimed at servers come wi
On Mon, Dec 12, 2011 at 12:39 PM, Gerd Hoffmann wrote:
> On 12/12/11 13:10, Stefan Hajnoczi wrote:
>> On Mon, Dec 12, 2011 at 11:29 AM, Gerd Hoffmann wrote:
>>> On 12/12/11 11:18, Stefan Hajnoczi wrote:
On Sun, Dec 11, 2011 at 10:29 AM, Alon Levy wrote:
> On Thu, Dec 08, 2011 at 05:45:4
On Mon, 12 Dec 2011 12:08:33 +, Stefan Hajnoczi wrote:
> On Fri, Dec 09, 2011 at 10:12:17PM +0530, M. Mohan Kumar wrote:
> > On Friday, December 09, 2011 12:01:14 AM Stefan Hajnoczi wrote:
> > > On Mon, Dec 05, 2011 at 09:48:41PM +0530, M. Mohan Kumar wrote:
> > > > +static int read_request(in
On Mon, 12 Dec 2011, Jan Kiszka wrote:
> Is there really no way to fix this properly in the Xen layer?
> >>>
> >>> We thought about this issue for some time but we couldn't come up with
> >>> anything better.
> >>> To summarize the problem:
> >>>
> >>> - on restore the videoram has already bee
On Mon, Dec 12, 2011 at 3:19 PM, takizo wrote:
>
> On Dec 12, 2011, at 11:08 PM, Stefan Hajnoczi wrote:
>
>> On Mon, Dec 12, 2011 at 2:50 PM, takizo wrote:
>>>
>>> On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote:
>>>
On Sun, Dec 11, 2011 at 4:40 PM, takizo wrote:
> LC_ALL=C PATH=/sbi
Am 12.12.2011 15:56, schrieb Paul Brook:
>> Am 12.12.2011 00:42, schrieb Paul Brook:
This series makes target-i386 compile with DEBUG_TCGV_TL.
>>>
>>> What benefit does this provide?
>>
>> It showcases what changes would need to be done to allow type-safe
>> compilation of the first pair of --
On ARM, don't map the code buffer at a fixed location, and fix up the
call/goto tcg routines to let it do long jumps.
Mapping the code buffer at a fixed address could sometimes result in it being
mapped over the top of the heap with pretty random results.
This diff is against v1.0.
Signed-off-by
On Dec 12, 2011, at 11:33 PM, Stefan Hajnoczi wrote:
> On Mon, Dec 12, 2011 at 3:19 PM, takizo wrote:
>>
>> On Dec 12, 2011, at 11:08 PM, Stefan Hajnoczi wrote:
>>
>>> On Mon, Dec 12, 2011 at 2:50 PM, takizo wrote:
On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote:
> On
On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
> Hi there,
>
> I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out that
> the command client_migrate_info uses it. That's a legacy interface and has to
> be dropped, no command should be using it...
>
Why has
CC'ing Andrzej, who is the tcg/arm maintainer.
On 12 December 2011 15:37, Dr. David Alan Gilbert
wrote:
> On ARM, don't map the code buffer at a fixed location, and fix up the
> call/goto tcg routines to let it do long jumps.
>
> Mapping the code buffer at a fixed address could sometimes result i
On Mon, Dec 12, 2011 at 3:21 PM, Aneesh Kumar K.V
wrote:
> On Mon, 12 Dec 2011 12:08:33 +, Stefan Hajnoczi
> wrote:
>> On Fri, Dec 09, 2011 at 10:12:17PM +0530, M. Mohan Kumar wrote:
>> > On Friday, December 09, 2011 12:01:14 AM Stefan Hajnoczi wrote:
>> > > On Mon, Dec 05, 2011 at 09:48:41P
> > Trying to make a 32-bit target "64-bit safe" without actually
> > implementing the 64-bit target is a complete waste of time.
>
> That's where we disagree. I rather do things right from the start than
> leaving the cleanup work to someone else later on.
>
> > You've almost no chance of getting
On Mon, Dec 12, 2011 at 03:23:35PM +, Stefan Hajnoczi wrote:
> On Mon, Dec 12, 2011 at 12:39 PM, Gerd Hoffmann wrote:
> > On 12/12/11 13:10, Stefan Hajnoczi wrote:
> >> On Mon, Dec 12, 2011 at 11:29 AM, Gerd Hoffmann wrote:
> >>> On 12/12/11 11:18, Stefan Hajnoczi wrote:
> On Sun, Dec 11
Please use git-send-email. This series won't apply via git-am as-is. Also, use
a single line separator with '---' between the revision history and the commit
message so that the revision history doesn't end up in git. You need to move
the SoB line before the revision history too.
Regards,
On Mon, 12 Dec 2011 17:50:46 +0200
Alon Levy wrote:
> On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
> > Hi there,
> >
> > I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out
> > that
> > the command client_migrate_info uses it. That's a legacy interface a
Patches introducing qemu_thread_join have floated around multiple times.
Now I found a bug that requires it to be fixed, so perhaps this time
it will be more successful.
For the actual bug, see patch 4.
v1->v2: remove spurious submodule change, fix blank lines
Jan Kiszka (2):
qemu-thread: add
From: Jan Kiszka
Allow to control if a QEMU thread is created joinable or not. Make it
not joinable by default to avoid that we keep the associated resources
around when terminating a thread without joining it (what we couldn't do
so far for obvious reasons).
The audio subsystem will need the jo
Destroying a mutex that another thread might have just unlocked
is racy. It usually works, but you cannot do that in general and
can lead to deadlocks or segfaults. Change ccid to use joinable
threads instead.
(Also, qemu_mutex_init/qemu_cond_init were missing).
Signed-off-by: Paolo Bonzini
--
From: Jan Kiszka
Split from Jan's original qemu-thread-posix.c patch. No semantic change,
just introduce the new API that POSIX and Win32 implementations will
conform to.
Signed-off-by: Jan Kiszka
Signed-off-by: Paolo Bonzini
---
cpus.c |6 --
hw/ccid-card-emulated.c
On 12/11/2011 04:29 AM, Alon Levy wrote:
On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
Hi there,
I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out that
the command client_migrate_info uses it. That's a legacy interface and has to
be dropped, no command
On 12/12/2011 10:00 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 03:23:35PM +, Stefan Hajnoczi wrote:
On Mon, Dec 12, 2011 at 12:39 PM, Gerd Hoffmann wrote:
On 12/12/11 13:10, Stefan Hajnoczi wrote:
On Mon, Dec 12, 2011 at 11:29 AM, Gerd Hoffmann wrote:
On 12/12/11 11:18, Stefan Hajnocz
On 12/12/2011 10:08 AM, Luiz Capitulino wrote:
On Mon, 12 Dec 2011 17:50:46 +0200
Alon Levy wrote:
On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
Hi there,
I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out that
the command client_migrate_info uses it.
On 12/12/2011 04:47 AM, Peter Maydell wrote:
The following changes since commit f18318eef8b4b263f4e82a5338c9b2875a6c73c8:
Merge branch 'master' of git://git.qemu.org/qemu (2011-12-12 04:12:31 +0400)
are available in the git repository at:
git://git.linaro.org/people/pmaydell/qemu-arm.git
On 12/06/2011 11:54 AM, Luiz Capitulino wrote:
Anthony,
This pull request contains my round 3 QAPI conversion patches, the new QMP
visitor tests, some documentation and the qmp test tool.
The changes (since 217bfb445b54db618a30f3a39170bebd9fd9dbf2) are available
in the following repository:
Rewrite the handshaking between qemu_thread_create and the
win32_start_routine, so that the thread can be joined without races.
Similar handshaking is done now between qemu_thread_exit and
qemu_thread_join.
This also simplifies how QemuThreads are initialized.
Signed-off-by: Paolo Bonzini
---
q
On 10/21/2011 09:03 AM, Paolo Bonzini wrote:
Even for files are licensed GPLv2-only, let's not play catch with
ourselves, and explicitly declare that future contributions to those
files will also be available as "any later version".
Signed-off-by: Paolo Bonzini
So where do we stand with this?
On Thu, Dec 08, 2011 at 12:52:19PM +0100, Jan Kiszka wrote:
> Changes in v4:
> - rebased of current uq/master
> - fixed stupid bugs that broke bisectability and user space irqchip mode
> - integrated NMI-over-LINT1 injection logic
>
> CC: Lai Jiangshan
>
> Jan Kiszka (15):
> msi: Generalize ms
On 10/24/2011 03:18 PM, Hervé Poussineau wrote:
NULL is a valid bus/device, so there is no change in behaviour.
Signed-off-by: Hervé Poussineau
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
---
arch_init.c|8
arch_init.h|2 +-
hw/adlib.c
On 10/24/2011 03:18 PM, Hervé Poussineau wrote:
Signed-off-by: Hervé Poussineau
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
---
hw/isa-bus.c |5 -
hw/isa.h |6 ++
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/hw/isa-bus.c b/hw/isa-bus.c
i
On 10/24/2011 03:18 PM, Hervé Poussineau wrote:
Signed-off-by: Hervé Poussineau
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
---
hw/i8259.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/i8259.c b/hw/i8259.c
index 4446339..7331e0e 100644
--- a/h
On 10/24/2011 03:18 PM, Hervé Poussineau wrote:
Signed-off-by: Hervé Poussineau
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
---
hw/pc.h |2 +-
hw/pc_piix.c |3 +--
hw/piix_pci.c |8 +---
3 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/h
On 10/24/2011 03:18 PM, Hervé Poussineau wrote:
Current patches are a rework of my patches already available at [1].
They don't provide full support for multiple ISA buses (yet), but
add a ISABus or ISADevice argument to all ISA functions.
They are mostly mechanically touching every instanciation
On 2011-12-12 17:37, Marcelo Tosatti wrote:
> On Thu, Dec 08, 2011 at 12:52:19PM +0100, Jan Kiszka wrote:
>> Changes in v4:
>> - rebased of current uq/master
>> - fixed stupid bugs that broke bisectability and user space irqchip mode
>> - integrated NMI-over-LINT1 injection logic
>>
>> CC: Lai Jian
On Mon, Dec 12, 2011 at 10:24:53AM -0600, Anthony Liguori wrote:
> On 12/12/2011 10:00 AM, Alon Levy wrote:
> >On Mon, Dec 12, 2011 at 03:23:35PM +, Stefan Hajnoczi wrote:
> >>On Mon, Dec 12, 2011 at 12:39 PM, Gerd Hoffmann wrote:
> >>>On 12/12/11 13:10, Stefan Hajnoczi wrote:
> On Mon, De
Hi,
On 12 December 2011 16:55, Peter Maydell wrote:
> On 12 December 2011 15:37, Dr. David Alan Gilbert
> wrote:
>> On ARM, don't map the code buffer at a fixed location, and fix up the
>> call/goto tcg routines to let it do long jumps.
>>
>> Mapping the code buffer at a fixed address could some
On 12/12/2011 06:51 PM, Jan Kiszka wrote:
> >
> > Any thoughts on the qemu-kvm merge plan? Sounds painful.
>
> Pain will be where the existing qemu-kvm extensions collide with these
> refactored upstream devices (backend/frontend split specifically).
> That's where we have to merge very carefully.
On 2011-12-12 18:37, Avi Kivity wrote:
> On 12/12/2011 06:51 PM, Jan Kiszka wrote:
>>>
>>> Any thoughts on the qemu-kvm merge plan? Sounds painful.
>>
>> Pain will be where the existing qemu-kvm extensions collide with these
>> refactored upstream devices (backend/frontend split specifically).
>> T
On 12/12/2011 11:22 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 10:24:53AM -0600, Anthony Liguori wrote:
On 12/12/2011 10:00 AM, Alon Levy wrote:
On Mon, Dec 12, 2011 at 03:23:35PM +, Stefan Hajnoczi wrote:
On Mon, Dec 12, 2011 at 12:39 PM, Gerd Hoffmann wrote:
On 12/12/11 13:10, Stefa
On 12/12/2011 07:42 PM, Jan Kiszka wrote:
> > It's a little late for this, but refactoring qemu-kvm in-tree and then
> > splitting it into patches would have been easier. Let's try it this way
> > for the next batch.
>
> I thought about this, but it definitely takes a clean, qemu-kvm free
> base a
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/569760
Title:
Error in i386 cmpxchg instruction emulation
Status in QEMU:
Fix Committed
Bug
On 12 December 2011 17:24, andrzej zaborowski wrote:
> BTW: I think we can also use the "ld" branch when we see the goto
> target is in Thumb mode.
The target of a goto is currently never Thumb (because gotos are
always to other TCG generated code and we only generate ARM insns).
If we did need t
On 12 December 2011 19:03, Peter Maydell wrote:
> On 12 December 2011 17:24, andrzej zaborowski wrote:
>> BTW: I think we can also use the "ld" branch when we see the goto
>> target is in Thumb mode.
>
> The target of a goto is currently never Thumb (because gotos are
> always to other TCG genera
On 12 December 2011 18:10, andrzej zaborowski wrote:
> On 12 December 2011 19:03, Peter Maydell wrote:
>> On 12 December 2011 17:24, andrzej zaborowski wrote:
>>> BTW: I think we can also use the "ld" branch when we see the goto
>>> target is in Thumb mode.
>>
>> The target of a goto is currentl
On 11/03/2011 08:03 PM, David Gibson wrote:
This patch removes some unnecessary casts in the eepro100 device,
introduced by commit 16ef60c9a8269f7cbc95219a431b1d7cbf29
'eepro100: Use PCI DMA stub functions'.
Signed-off-by: David Gibson
Applied all. Thanks.
Regards,
Anthony Liguori
---
On 11/09/2011 03:09 PM, Peter Maydell wrote:
"!X == 2" is always false (spotted by Coverity), so the checks
for whether rndis is in the correct state would never fire.
Signed-off-by: Peter Maydell
Applied. Thanks.
Regards,
Anthony Liguori
---
NB that although I tested that this doesn't br
On 11/10/2011 06:41 AM, Eduardo Habkost wrote:
Comments for v3:
I am still not sure if this is 1.0 material, but I am more inclined to delay
this for post-1.0.
Changes v2 -> v3:
- Only coding style changes for issues detected by checkpatch.pl:
- Avoid "//" comments;
- Use braces on if s
On 12/08/2011 04:51 PM, Blue Swirl wrote:
Why limit this to device emulation only? Where in QEMU would this
approach not work?
That's a good point, and we've thrown this idea around. I don't know if
there's any reason why this approach wouldn't work for all of QEMU. The
idea for now thoug
On Sun, Dec 11, 2011 at 4:50 AM, Dor Laor wrote:
> On 12/08/2011 11:40 AM, Stefan Hajnoczi wrote:
>>
>> On Wed, Dec 7, 2011 at 8:54 PM, Eric Paris wrote:
>>>
>>> On Wed, 2011-12-07 at 13:43 -0600, Anthony Liguori wrote:
On 12/07/2011 01:32 PM, Corey Bryant wrote:
>>>
>>>
> That woul
1 - 100 of 261 matches
Mail list logo
