The patches has been rebased onto Alex's [RFC] [PATCHv5 00/16] aio / timers:
Add AioContext timers and use ppoll
permalink.gmane.org/gmane.comp.emulators.qemu/226333
For some other complied error issue, I can not finish compiling, will fix it
later.
Changes since last version:
1. drop the
In kvm mode, vm_clock may be read outside BQL. This will make
timers_state --the foundation of vm_clock exposed to race condition.
Using private lock to protect it.
Note in tcg mode, vm_clock still read inside BQL, so icount is
left without change. As for cpu_ticks in timers_state, it
is still pro
From: Paolo Bonzini
This lets the read-side access run outside the BQL.
Signed-off-by: Paolo Bonzini
---
include/qemu/seqlock.h | 72 ++
1 file changed, 72 insertions(+)
create mode 100644 include/qemu/seqlock.h
diff --git a/include/qemu/seqloc
After disabling the QemuClock, we should make sure that no QemuTimers
are still in flight. To implement that with light overhead, we resort
to QemuEvent. The caller of disabling will wait on QemuEvent of each
timerlist.
Note, qemu_clock_enable(foo,false) can _not_ be called from timer's cb.
And th
From: Paolo Bonzini
This emulates Win32 manual-reset events using futexes or conditional
variables. Typical ways to use them are with multi-producer,
single-consumer data structures, to test for a complex condition whose
elements come from different threads:
for (;;) {
qemu_event_re
On 03/08/13 23:01, Aurelien Jarno wrote:
> On Thu, Aug 01, 2013 at 11:02:27AM +0100, Leon Alrae wrote:
>> These are not DSP instructions, thus there is no "ac" field.
>>
>> For more details please refer to instruction encoding of
>> MULT, MULTU, MADD, MADDU, MSUB, MSUBU, MFHI, MFLO, MTHI, MTLO in
>
On 08/01/13 16:31, Luiz Capitulino wrote:
> On Thu, 1 Aug 2013 09:41:07 -0400
> Luiz Capitulino wrote:
>
>> Applied to the qmp branch, thanks.
>
> Hmm, it brakes the build. Dropping it from the queue for now:
>
> /home/lcapitulino/work/src/upstream/qmp-unstable/target-s390x/arch_dump.c:179:5:
>
On Sun, Aug 04, 2013 at 03:36:52PM +0200, Oliver Francke wrote:
> Am 02.08.2013 um 23:47 schrieb Mike Dawson :
> > We can "un-wedge" the guest by opening a NoVNC session or running a 'virsh
> > screenshot' command. After that, the guest resumes and runs as expected. At
> > that point we can exami
From: MORITA Kazutaka
While Asias is debugging an issue creating qcow2 images on top of
non-file protocols. It boils down to this example using NBD:
$ qemu-io -c 'open -g nbd+unix:///?socket=/tmp/nbd.sock' -c 'read -v 0 512'
Notice the open -g option to set bs->growable. This means you can
re
v1->v2 [Luiz]:
- fix up the cpu_get_dump_info() prototype in "target-s390x/arch_dump.c"
that has been introduced between my posting of v1 and Luiz's applying
it to qmp-1.6. (Patch #4.)
v1 blurb:
Conceptually, the dump-guest-memory command works as follows:
(a) pause the guest,
(b) get a snaps
The vmcore must use physical addresses that are visible to the guest, not
addresses that point into linear RAMBlocks. As first step, introduce the
list type into which we'll collect the physical mappings in effect at the
time of the dump.
Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=9
Even a trusted & clean-state guest can map more memory than what it was
given. Since the vmcore contains RAMBlocks, mapping sizes should be
clamped to RAMBlock sizes. Otherwise such oversized mappings can exceed
the entire file size, and ELF parsers might refuse even the valid portion
of the PT_LOA
RAMBlock.offset --> GuestPhysBlock.target_start
RAMBlock.offset + RAMBlock.length --> GuestPhysBlock.target_end
RAMBlock.length --> GuestPhysBlock.target_end -
GuestPhysBlock.target_start
"GuestPhysBlock.host_addr" is only u
Signed-off-by: Gal Hammer
---
hw/char/virtio-serial-bus.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c
index da417c7..0d38b4b 100644
--- a/hw/char/virtio-serial-bus.c
+++ b/hw/char/virtio-serial-bus.c
@@ -105,6
While the machine is paused, in guest_phys_blocks_append() we register a
one-shot MemoryListener, solely for the initial collection of the valid
guest-physical memory ranges that happens at client registration time.
For each range that is reported to guest_phys_blocks_set_memory(), we
attempt to m
Am 05.08.2013 07:43, schrieb Paul Mackerras:
> On Fri, Aug 02, 2013 at 06:14:46PM +0200, Andreas Färber wrote:
>> Am 02.08.2013 04:59, schrieb Alexey Kardashevskiy:
>>> This patch adds CPU PVR definition for POWER7+.
>>>
>>> Signed-off-by: Alexey Kardashevskiy
>>> ---
>>> target-ppc/cpu-models.c
>> >> >> hi all,
>> >> >>
>> >> >> I met similar problem to these, while performing live migration or
>> >> >> save-restore test on the kvm platform (qemu:1.4.0, host:suse11sp2,
>> >> >> guest:suse11sp2), running tele-communication software suite in
>> >> >> guest,
>> >> >> https://lists.gnu.o
On Mon, Aug 05, 2013 at 08:35:09AM +, Zhanghaoyu (A) wrote:
> >> >> >> hi all,
> >> >> >>
> >> >> >> I met similar problem to these, while performing live migration or
> >> >> >> save-restore test on the kvm platform (qemu:1.4.0, host:suse11sp2,
> >> >> >> guest:suse11sp2), running tele-comm
Am 05.08.2013 00:04, schrieb Aurélien Jarno:
> On Mon, Jul 29, 2013 at 10:35:31PM +0200, Stefan Weil wrote:
>> Am 27.07.2013 22:58, schrieb Stefan Weil:
>>> Am 27.07.2013 22:43, schrieb Andreas Färber:
Am 27.07.2013 21:37, schrieb Stefan Weil:
> Am 27.07.2013 19:43, schrieb Peter Maydell:
On 2013-08-05 10:45, Andreas Färber wrote:
> Am 05.08.2013 00:04, schrieb Aurélien Jarno:
>> On Mon, Jul 29, 2013 at 10:35:31PM +0200, Stefan Weil wrote:
>>> Am 27.07.2013 22:58, schrieb Stefan Weil:
Am 27.07.2013 22:43, schrieb Andreas Färber:
> Am 27.07.2013 21:37, schrieb Stefan Weil:
>
On 07/26/2013 05:41 PM, Paolo Bonzini wrote:
Il 25/07/2013 22:18, Lei Li ha scritto:
Hi,
This patch series tries to add localhost migration support to
Qemu.
When doing localhost migration, the host memory will balloon
up during the period, might consume double memories for some time.
So we wan
Don't silently ignore excess arguments at the end of the command line,
but error out instead. This can catch typos like 'resize test.img + 1G',
which doesn't increase the image size by 1G as intended, but truncates
the image to 1G. Even for less dangerous commands, the old behaviour is
confusing.
PING? any comments?
On 07/24/2013 11:48 PM, Lei Li wrote:
In the logic of ram_save_iterate(), it checks the ret of
qemu_file_rate_limit(f)
by ret < 0 if there has been an error. But now it will never return
negative value
because qemu_file_rate_limit() return 1 if qemu_file_get_error().
Also
>> >> >> >> hi all,
>> >> >> >>
>> >> >> >> I met similar problem to these, while performing live migration or
>> >> >> >> save-restore test on the kvm platform (qemu:1.4.0, host:suse11sp2,
>> >> >> >> guest:suse11sp2), running tele-communication software suite in
>> >> >> >> guest,
>> >> >> >
On Mon, 2013-08-05 at 10:24 +0200, Andreas Färber wrote:
> Ben has pointed out that POWER5++ PVR-wise was a POWER5+ v3.0+ or so
> and, according to you, POWER5++ is not just a revision with
> hardware-only changes and a new marketing name. So no, it's not always
> just the upper 16 bits.
Also 4xx
Hi,
Am 05.08.2013 11:09, schrieb Zhanghaoyu (A):
> When I build the upstream, encounter a problem that I compile and install the
> upstream(commit: e769ece3b129698d2b09811a6f6d304e4eaa8c29) on sles11sp2
> environment via below command
> cp /boot/config-3.0.13-0.27-default ./.config
> yes "" | ma
Signed-off-by: Gerd Hoffmann
---
hw/pci-bridge/i82801b11.c |1 +
1 file changed, 1 insertion(+)
diff --git a/hw/pci-bridge/i82801b11.c b/hw/pci-bridge/i82801b11.c
index 8a5e426..14cd7fd 100644
--- a/hw/pci-bridge/i82801b11.c
+++ b/hw/pci-bridge/i82801b11.c
@@ -90,6 +90,7 @@ static void i8280
On 5 August 2013 02:21, Peter Chubb wrote:
> Reads to unassigned memory now return non-zero (since patch
> 9b8c69243585). This breaks guests runnong on i.MX31 that use the
> cache controller --- they poll forever waiting for the L2CC cache
> invalidate regsiter to be zero.
That commit claims it w
>Hi,
>
>Am 05.08.2013 11:09, schrieb Zhanghaoyu (A):
>> When I build the upstream, encounter a problem that I compile and
>> install the upstream(commit: e769ece3b129698d2b09811a6f6d304e4eaa8c29)
>> on sles11sp2 environment via below command cp
>> /boot/config-3.0.13-0.27-default ./.config yes "
Am 05.08.2013 11:18, schrieb Peter Maydell:
> On 5 August 2013 02:21, Peter Chubb wrote:
>> Reads to unassigned memory now return non-zero (since patch
>> 9b8c69243585). This breaks guests runnong on i.MX31 that use the
>> cache controller --- they poll forever waiting for the L2CC cache
>> invali
On Fri, Aug 02, 2013 at 06:30:52PM +0200, Vincenzo Maffione wrote:
> This patch partially implements the e1000 interrupt mitigation mechanisms.
> Using a single QEMUTimer, it emulates the ITR register (which is the newer
> mitigation register, recommended by Intel) and approximately emulates
> RADV
On Fri, Aug 02, 2013 at 06:30:52PM +0200, Vincenzo Maffione wrote:
> This patch partially implements the e1000 interrupt mitigation mechanisms.
> Using a single QEMUTimer, it emulates the ITR register (which is the newer
> mitigation register, recommended by Intel) and approximately emulates
> RADV
Am 03.08.2013 10:31, schrieb Jan Kiszka:
> From: Jan Kiszka
>
> Accesses to unassigned io ports shall return -1 on read and be ignored
> on write. Ensure these properties via dedicated ops, decoupling us from
> the memory core's handling of unassigned accesses.
>
> Signed-off-by: Jan Kiszka
> -
On Mon, Aug 05, 2013 at 09:09:56AM +, Zhanghaoyu (A) wrote:
> The QEMU command line (/var/log/libvirt/qemu/[domain name].log),
> LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none
> /usr/local/bin/qemu-system-x86_64 -name ATS1 -S -M pc-0.12 -cpu qemu32
> -enable-kvm -m 122
On 2013-08-05 11:34, Andreas Färber wrote:
> Am 03.08.2013 10:31, schrieb Jan Kiszka:
>> From: Jan Kiszka
>>
>> Accesses to unassigned io ports shall return -1 on read and be ignored
>> on write. Ensure these properties via dedicated ops, decoupling us from
>> the memory core's handling of unassig
Am 05.08.2013 11:27, schrieb Stefan Hajnoczi:
> On Fri, Aug 02, 2013 at 06:30:52PM +0200, Vincenzo Maffione wrote:
>> This patch partially implements the e1000 interrupt mitigation mechanisms.
>> Using a single QEMUTimer, it emulates the ITR register (which is the newer
>> mitigation register, reco
Am 05.08.2013 10:50, schrieb Gerd Hoffmann:
> Signed-off-by: Gerd Hoffmann
> ---
> hw/pci-bridge/i82801b11.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/pci-bridge/i82801b11.c b/hw/pci-bridge/i82801b11.c
> index 8a5e426..14cd7fd 100644
> --- a/hw/pci-bridge/i82801b11.c
> +++ b
On 5 August 2013 10:34, Andreas Färber wrote:
> Am 03.08.2013 10:31, schrieb Jan Kiszka:
>> From: Jan Kiszka
>>
>> Accesses to unassigned io ports shall return -1 on read and be ignored
>> on write. Ensure these properties via dedicated ops, decoupling us from
>> the memory core's handling of una
Pingfan,
--On 5 August 2013 15:33:22 +0800 Liu Ping Fan
wrote:
The patches has been rebased onto Alex's [RFC] [PATCHv5 00/16] aio /
timers: Add AioContext timers and use ppoll
permalink.gmane.org/gmane.comp.emulators.qemu/226333
For some other complied error issue, I can not finish compilin
Am 05.08.2013 11:59, schrieb Peter Maydell:
> On 5 August 2013 10:34, Andreas Färber wrote:
>> Am 03.08.2013 10:31, schrieb Jan Kiszka:
>>> From: Jan Kiszka
>>>
>>> Accesses to unassigned io ports shall return -1 on read and be ignored
>>> on write. Ensure these properties via dedicated ops, deco
On 2013-08-05 11:59, Peter Maydell wrote:
> On 5 August 2013 10:34, Andreas Färber wrote:
>> Am 03.08.2013 10:31, schrieb Jan Kiszka:
>>> From: Jan Kiszka
>>>
>>> Accesses to unassigned io ports shall return -1 on read and be ignored
>>> on write. Ensure these properties via dedicated ops, decoup
On 08/05/13 11:45, Andreas Färber wrote:
> Am 05.08.2013 10:50, schrieb Gerd Hoffmann:
>> Signed-off-by: Gerd Hoffmann
>> ---
>> hw/pci-bridge/i82801b11.c |1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/pci-bridge/i82801b11.c b/hw/pci-bridge/i82801b11.c
>> index 8a5e426..14cd7fd
On 5 August 2013 11:30, Jan Kiszka wrote:
> On 2013-08-05 11:59, Peter Maydell wrote:
>> Or do you mean that if we had:
>>
>> [ system memory region, with its own default read/write ops ]
>
> I cannot imagine how this could work. The system memory region has no
> clue about what the regions below
On 2013-08-05 12:36, Peter Maydell wrote:
> On 5 August 2013 11:30, Jan Kiszka wrote:
>> On 2013-08-05 11:59, Peter Maydell wrote:
>>> Or do you mean that if we had:
>>>
>>> [ system memory region, with its own default read/write ops ]
>>
>> I cannot imagine how this could work. The system memory
On Mon, Aug 05, 2013 at 08:41:52AM +0100, Leon Alrae wrote:
> On 03/08/13 23:01, Aurelien Jarno wrote:
> > On Thu, Aug 01, 2013 at 11:02:27AM +0100, Leon Alrae wrote:
> >> These are not DSP instructions, thus there is no "ac" field.
> >>
> >> For more details please refer to instruction encoding of
On 5 August 2013 11:44, Jan Kiszka wrote:
> On 2013-08-05 12:36, Peter Maydell wrote:
>> On 5 August 2013 11:30, Jan Kiszka wrote:
>>> On 2013-08-05 11:59, Peter Maydell wrote:
Or do you mean that if we had:
[ system memory region, with its own default read/write ops ]
>>>
>>> I c
On Aug 05 2013, Liu Ping Fan wrote:
> After disabling the QemuClock, we should make sure that no QemuTimers
> are still in flight. To implement that with light overhead, we resort
> to QemuEvent. The caller of disabling will wait on QemuEvent of each
> timerlist.
>
> Note, qemu_clock_enable(foo,f
On 2013-08-05 12:51, Peter Maydell wrote:
> On 5 August 2013 11:44, Jan Kiszka wrote:
>> On 2013-08-05 12:36, Peter Maydell wrote:
>>> On 5 August 2013 11:30, Jan Kiszka wrote:
On 2013-08-05 11:59, Peter Maydell wrote:
> Or do you mean that if we had:
>
> [ system memory region,
The 'int' loglevel for recording interrupts and exceptions
requires support in the target-specific code. Implement
it for ARM. This improves debug logging in some situations
that were otherwise pretty opaque, such as when we fault
trying to execute at an exception vector address, which
would otherw
On Aug 05 2013, Jan Kiszka wrote:
> On 2013-08-05 12:36, Peter Maydell wrote:
> > On 5 August 2013 11:30, Jan Kiszka wrote:
> >> On 2013-08-05 11:59, Peter Maydell wrote:
> >>> Or do you mean that if we had:
> >>>
> >>> [ system memory region, with its own default read/write ops ]
> >>
> >> I ca
On Aug 05 2013, Peter Maydell wrote:
> > But even if we would, the IO container now catches all accesses, so
> > the system memory region will never have its default handler run for
> > that window.
>
> Yes, that is the point -- before the IO container caught all
> accesses, the default handler th
This patch series adds a 'virt' platform which uses the
kernel's mach-virt (fully device-tree driven) support
to create a simple minimalist platform intended for
use for KVM VM guests. It's based on John Rigby's
patches, but I've overhauled it a lot:
* renamed user-facing machine to just "virt"
From: John Rigby
If no fdt is provided on command line and the new field
get_dtb in struct arm_boot_info is set then call it to
get a device tree blob.
Signed-off-by: John Rigby
[PMM: minor tweaks and cleanup]
Signed-off-by: Peter Maydell
---
hw/arm/boot.c| 32 --
On 5 August 2013 12:18, Peter Maydell wrote:
> From: John Rigby
>
> Add 'virt' platform support corresponding to arch/arm/mach-virt
> in the Linux kernel tree. This has no platform-specific code but
> can use any device whose kernel driver is is able to work purely
> from a device tree node. We u
From: John Rigby
Add 'virt' platform support corresponding to arch/arm/mach-virt
in the Linux kernel tree. This has no platform-specific code but
can use any device whose kernel driver is is able to work purely
from a device tree node. We use this to instantiate a minimal
set of devices: a GIC an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 05.08.2013 13:03, schrieb Jan Kiszka:
> On 2013-08-05 12:51, Peter Maydell wrote:
>> On 5 August 2013 11:44, Jan Kiszka wrote:
>>> On 2013-08-05 12:36, Peter Maydell wrote:
On 5 August 2013 11:30, Jan Kiszka
wrote:
> On 2013-08-05 11
On Fri, Aug 02, 2013 at 09:41:24PM +0200, Jan Kiszka wrote:
> On 2013-08-02 14:45, Jan Kiszka wrote:
> > On 2013-08-02 13:46, Stefan Hajnoczi wrote:
> >> On Thu, Aug 01, 2013 at 07:15:54PM +0200, Jan Kiszka wrote:
> >>> I was digging into the involved code and found something fishy:
> >>>
> >>> net
On 2013-08-05 13:35, Andreas Färber wrote:
> Am 05.08.2013 13:03, schrieb Jan Kiszka:
>> On 2013-08-05 12:51, Peter Maydell wrote:
>>> On 5 August 2013 11:44, Jan Kiszka wrote:
On 2013-08-05 12:36, Peter Maydell wrote:
> On 5 August 2013 11:30, Jan Kiszka
> wrote:
>> On 2013-08-0
On 08/05/13 10:57, Kevin Wolf wrote:
> Don't silently ignore excess arguments at the end of the command line,
> but error out instead. This can catch typos like 'resize test.img + 1G',
> which doesn't increase the image size by 1G as intended, but truncates
> the image to 1G. Even for less dangerou
Am 01.08.2013 um 05:23 hat Jeff Cody geschrieben:
> This adds the ability to update the headers in a VHDX image, including
> generating a new MS-compatible GUID.
>
> As VHDX depends on uuid.h, VHDX is now a configurable build option. If
> VHDX support is enabled, that will also enable uuid as wel
On 08/05/13 10:18, Gal Hammer wrote:
> Signed-off-by: Gal Hammer
> ---
> hw/char/virtio-serial-bus.c | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c
> index da417c7..0d38b4b 100644
> --- a/hw/char/virtio-seri
On Mon, Aug 5, 2013 at 4:48 PM, Peter Maydell wrote:
> From: John Rigby
>
> Add 'virt' platform support corresponding to arch/arm/mach-virt
> in the Linux kernel tree. This has no platform-specific code but
> can use any device whose kernel driver is is able to work purely
> from a device tree no
Am 03.08.2013 um 05:52 hat Doug Goldstein geschrieben:
> On Tue, Jul 23, 2013 at 4:19 AM, Paolo Bonzini wrote:
> > Il 23/07/2013 10:30, MORITA Kazutaka ha scritto:
> >> This prevents the tools from being stopped when they write data to a
> >> closed connection in the other side.
> >>
> >> Signed-o
On Sat, Aug 03, 2013 at 10:20:41PM -0400, Brad Smith wrote:
> The following patch simplifies the *BSD tap/tun code and makes use of numbered
> tap/tun interfaces on all *BSD OS's. NetBSD has a patch in their pkgsrc tree
> to make use of this feature and DragonFly also supports this as well.
>
> Si
On 08/04/13 14:17, Mark Cave-Ayland wrote:
> On 01/08/13 23:08, Anthony Liguori wrote:
>
>> Hi,
>>
>> On behalf of the QEMU Team, I'd like to announce the availability of the
>> second release candidate for the QEMU 1.6 release. This release is meant
>> for testing purposes and should not be used
On Fri, Aug 02, 2013 at 09:47:08PM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Each networking client has a queue for packets that could not yet be
> delivered to that client. Calling this queue "send_queue" is highly
> confusing as it has nothing to to with packets send from this client but
On 05/08/2013 14:49, Laszlo Ersek wrote:
On 08/05/13 10:18, Gal Hammer wrote:
Signed-off-by: Gal Hammer
---
hw/char/virtio-serial-bus.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c
index da417c7..0d38b4b 10
Am 02.08.2013 19:22, schrieb Andreas Färber:
> Error **errp argument is not for emitting warnings, it means an error
> has occurred and the caller should not make any assumptions about the
> state of other return values (unless otherwise documented).
>
> Therefore cpu_x86_create() must unref the n
On 2013-08-05 14:06, Andreas Färber wrote:
> Am 02.08.2013 19:22, schrieb Andreas Färber:
>> Error **errp argument is not for emitting warnings, it means an error
>> has occurred and the caller should not make any assumptions about the
>> state of other return values (unless otherwise documented).
On Fri, Aug 02, 2013 at 09:48:18PM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Analogously to other NICs, we have to inform the network layer when
> the can_receive handler will no longer report 0. Without this, we may
> get stuck waiting on queued incoming packets.
>
> Signed-off-by: Jan Ki
On 5 August 2013 12:48, Anup Patel wrote:
>> +static const MemMapEntry a15memmap[] = {
>> +[VIRT_FLASH] = { 0, 0x10 },
>
> IMHO, 1 MB of flash is small for possible future expansion. If mach-virt
> becomes popular then we can expect people running UBoot or UEFI or
> from this flash.
>
From: Jan Kiszka
Analogously to other NICs, we have to inform the network layer when
the can_receive handler will no longer report 0. Without this, we may
get stuck waiting on queued incoming packets.
Signed-off-by: Jan Kiszka
Signed-off-by: Stefan Hajnoczi
---
hw/net/pcnet.c | 4
1 file
This fix allows the pcnet NIC to work properly with the tap device.
The following changes since commit b9ac5d923b820a0f0152a2df56067e55ce34f487:
target-mips: fix 34Kf configuration for DSP ASE (2013-08-03 23:33:17 +0200)
are available in the git repository at:
git://github.com/stefanha/qemu
On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell wrote:
> On 5 August 2013 12:48, Anup Patel wrote:
>>> +static const MemMapEntry a15memmap[] = {
>>> +[VIRT_FLASH] = { 0, 0x10 },
>>
>> IMHO, 1 MB of flash is small for possible future expansion. If mach-virt
>> becomes popular then we can exp
On Mon, Aug 05, 2013 at 07:19:08AM +0200, Stefan Weil wrote:
> Am 05.08.2013 00:37, schrieb Peter Maydell:
> > On 4 August 2013 23:04, Aurélien Jarno wrote:
> >> The real hardware probably returns all 1 or all 0 for addresses not
> >> decoded to a device. This is what QEMU should model, and it sho
On 5 August 2013 13:22, Anup Patel wrote:
> On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell
> wrote:
>> On 5 August 2013 12:48, Anup Patel wrote:
+static const MemMapEntry a15memmap[] = {
+[VIRT_FLASH] = { 0, 0x10 },
>>>
>>> IMHO, 1 MB of flash is small for possible future expan
Am 03.08.2013 um 05:48 hat Doug Goldstein geschrieben:
> On Tue, Jul 23, 2013 at 6:28 AM, Paolo Bonzini wrote:
> > Il 23/07/2013 10:30, MORITA Kazutaka ha scritto:
> >> Without this patch, iov_send_recv() never returns when do_send_recv()
> >> returns zero.
> >>
> >> Signed-off-by: MORITA Kazutaka
On Mon, Aug 5, 2013 at 5:58 PM, Peter Maydell wrote:
> On 5 August 2013 13:22, Anup Patel wrote:
>> On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell
>> wrote:
>>> On 5 August 2013 12:48, Anup Patel wrote:
> +static const MemMapEntry a15memmap[] = {
> +[VIRT_FLASH] = { 0, 0x10 },
>
Am 05.08.2013 um 10:11 hat Asias He geschrieben:
> From: MORITA Kazutaka
>
> While Asias is debugging an issue creating qcow2 images on top of
> non-file protocols. It boils down to this example using NBD:
>
> $ qemu-io -c 'open -g nbd+unix:///?socket=/tmp/nbd.sock' -c 'read -v 0 512'
>
> Noti
On 5 August 2013 13:37, Anup Patel wrote:
> On Mon, Aug 5, 2013 at 5:58 PM, Peter Maydell
> wrote:
>> I really don't want to eat 2MB for each virtio-mmio transport
>> in a 32 bit address space, it seems hugely wasteful unless
>> there's a good reason to do it.
>
> I am not suggesting to give 2MB
On Mon, Aug 05, 2013 at 12:18:10PM +0100, Peter Maydell wrote:
> This patch series adds a 'virt' platform which uses the
> kernel's mach-virt (fully device-tree driven) support
> to create a simple minimalist platform intended for
> use for KVM VM guests. It's based on John Rigby's
> patches, but I
On 05/08/13 11:50, Aurelien Jarno wrote:
> On Mon, Aug 05, 2013 at 08:41:52AM +0100, Leon Alrae wrote:
>> On 03/08/13 23:01, Aurelien Jarno wrote:
>>> On Thu, Aug 01, 2013 at 11:02:27AM +0100, Leon Alrae wrote:
These are not DSP instructions, thus there is no "ac" field.
For more det
Filter out the QEMU monitor version banner so that tests do not break
when the QEMU version number is changed.
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/051.out | 64
tests/qemu-iotests/common.filter | 3 +-
2 files changed, 34 insertio
On 5 August 2013 13:49, Daniel P. Berrange wrote:
> On x86, we've long had versioned machine names, so that we can
> make changes in future QEMU releases without breaking guest ABI
> compatibility. AFAICT, the problem has basically been ignored
> on non-x86 platforms in QEMU.
Yes; this is deliber
Hi,
> -Original Message-
> From: Gonglei (Arei)
> Sent: Tuesday, July 30, 2013 10:01 AM
> To: 'Pasi Kärkkäinen'
> Cc: Gerd Hoffmann; Andreas Färber; Hanweidong; Luonengjun;
> qemu-devel@nongnu.org; xen-de...@lists.xen.org; Anthony Liguori;
> Huangweidong (Hardware); 'ian.jack...@eu.citrix.c
On 18 July 2013 14:31, Peter Maydell wrote:
> On 1 July 2013 20:07, Peter Maydell wrote:
>> On 1 July 2013 18:34, Peter Maydell wrote:
>>> This patchset is v5 of the "preparation patchset" that started
>>> off with Alex, was passed to John Rigby and now to me.
>>
>> Also available via git:
>>
>>
On Mon, 05 Aug 2013 14:01:10 +0200
Laszlo Ersek wrote:
> Please do consider it for 1.6, it addresses a serious bug (= vmcores saved
> with dump-guest-memory/paging=false are broken for > 3.5G x86(_64) guests).
No worries, it is going to be included (unless someone has a serious objection,
of cou
Hello Anthony/Aurélien,
This series extends test coverage to all 16 targets.
For now it tests that QOM type changes do not lead to QOM cast assertions.
v2 extends it to cover virtually all machines (except Xen and pc*-x.y).
Where an fprintf() is touched, use error_report() instead.
Regards,
Andr
Signed-off-by: Andreas Färber
---
hw/arm/z2.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/arm/z2.c b/hw/arm/z2.c
index 07a127b..a4cbaeb 100644
--- a/hw/arm/z2.c
+++ b/hw/arm/z2.c
@@ -24,6 +24,7 @@
#include "ui/console.h"
#include "audio/audio.h"
#include "exec/a
Signed-off-by: Andreas Färber
---
hw/arm/boot.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index 2cbeefd..0c6d611 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -15,6 +15,7 @@
#include "hw/loader.h"
#include "elf.h"
#include "sysemu/device_tree.h"
Signed-off-by: Andreas Färber
---
hw/mips/mips_mipssim.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/mips/mips_mipssim.c b/hw/mips/mips_mipssim.c
index fea1a15..d8c4347 100644
--- a/hw/mips/mips_mipssim.c
+++ b/hw/mips/mips_mipssim.c
@@ -37,6 +37,7 @@
#include "elf.
Also move one stray debug output into an #ifdef.
Signed-off-by: Andreas Färber
---
hw/ppc/ppc405_boards.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/ppc/ppc405_boards.c b/hw/ppc/ppc405_boards.c
index f74e5e5..807ada0 100644
--- a/hw/ppc/ppc405_boards.c
+++ b/hw/pp
Signed-off-by: Andreas Färber
---
hw/cris/axis_dev88.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/hw/cris/axis_dev88.c b/hw/cris/axis_dev88.c
index 9104d61..6673c66 100644
--- a/hw/cris/axis_dev88.c
+++ b/hw/cris/axis_dev88.c
@@ -32,6 +32,7 @@
#include "boot.
Signed-off-by: Andreas Färber
---
hw/arm/gumstix.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/hw/arm/gumstix.c b/hw/arm/gumstix.c
index b8cab10..a9015ed 100644
--- a/hw/arm/gumstix.c
+++ b/hw/arm/gumstix.c
@@ -42,6 +42,7 @@
#include "hw/boards.h"
#include "s
Simply skip flash setup for now.
Also drop useless debug output.
Signed-off-by: Andreas Färber
---
hw/arm/mainstone.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/arm/mainstone.c b/hw/arm/mainstone.c
index 8e5fc26..e9d4b98 100644
--- a/hw/arm/mainstone.c
+++ b/hw/a
Signed-off-by: Andreas Färber
---
hw/arm/palm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/arm/palm.c b/hw/arm/palm.c
index cdc3c3a..dc4bbcd 100644
--- a/hw/arm/palm.c
+++ b/hw/arm/palm.c
@@ -19,6 +19,7 @@
#include "hw/hw.h"
#include "audio/audio.h"
#include "syse
"Daniel P. Berrange" writes:
> On Mon, Aug 05, 2013 at 12:18:10PM +0100, Peter Maydell wrote:
>> This patch series adds a 'virt' platform which uses the
>> kernel's mach-virt (fully device-tree driven) support
>> to create a simple minimalist platform intended for
>> use for KVM VM guests. It's b
Signed-off-by: Andreas Färber
---
hw/lm32/milkymist.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/lm32/milkymist.c b/hw/lm32/milkymist.c
index 7ceedb8..a8e7230 100644
--- a/hw/lm32/milkymist.c
+++ b/hw/lm32/milkymist.c
@@ -21,6 +21,7 @@
#include "hw/hw.h"
#include "
Adopt error_report() while at it.
Signed-off-by: Andreas Färber
---
hw/ppc/ppc405_boards.c | 35 ---
1 file changed, 20 insertions(+), 15 deletions(-)
diff --git a/hw/ppc/ppc405_boards.c b/hw/ppc/ppc405_boards.c
index 807ada0..75b2177 100644
--- a/hw/ppc/ppc405_b
Instantiate all [*] machines per target, so that they get a bit of test
coverage at all. This has proven helpful during QOM refactorings.
[*] ppcemb target contains some non-working non-embedded machines, and
ppc405 CPUs are not available there either.
i386 and x86_64 do not cover pc*-x.y or xenfv
1 - 100 of 244 matches
Mail list logo
