On Sun, 22 Apr 2018 12:05:44 -0400
Tony Krowiak wrote:
> On 04/19/2018 08:03 AM, Cornelia Huck wrote:
> > On Sun, 15 Apr 2018 15:07:23 -0400
> > Tony Krowiak wrote:
> >
> >> Introduces a VFIO based AP device. The device is defined via
> >> the QEMU command line by specifying:
> >>
> >> -d
On Sun, 22 Apr 2018 12:17:22 -0400
Tony Krowiak wrote:
> On 04/19/2018 07:51 AM, Cornelia Huck wrote:
> > On Sun, 15 Apr 2018 15:07:19 -0400
> > Tony Krowiak wrote:
> >
> >> default-configs/s390x-softmmu.mak |1 +
> >> docs/vfio-ap.txt | 649
> >> +
On 04/23/2018 05:59 AM, David Gibson wrote:
> On Fri, Apr 20, 2018 at 10:27:21AM +0200, Cédric Le Goater wrote:
>> On 04/20/2018 09:10 AM, David Gibson wrote:
>>> On Thu, Apr 19, 2018 at 02:42:57PM +0200, Cédric Le Goater wrote:
Each XIVE interrupt source is associated with a two bit state mac
On 04/23/2018 08:44 AM, David Gibson wrote:
> On Thu, Apr 19, 2018 at 02:42:58PM +0200, Cédric Le Goater wrote:
>> The 'sent' status of the LSI interrupt source is modeled with the 'P'
>> bit of the ESB and the assertion status of the source is maintained in
>> an array under the main sPAPRXive obj
Hello,
This is v2 of:
https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg00783.html
Compared to v1, I have addressed Peter's comments:
- patch #1 removes CONFIG_USE_FDPIC
- patch #2 corresponds to the previous patch #1, and is now simpler
without configure option
- patch #3 corresponds to
The FDPIC restorer needs to deal with a function descriptor, hence we
have to extend 'retcode' such that it can hold the instructions needed
to perform this.
The restorer sequence uses the same thumbness as the exception
handler (mainly to support Thumb-only architectures).
Co-Authored-By: Mickaë
We want to avoid code disabled by default, because it ends up less
tested. This patch removes all instances of #ifdef CONFIG_USE_FDPIC,
most of which can be safely kept. For the ones that should be
conditionally executed, we define elf_is_fdpic(). Without this patch,
defining CONFIG_USE_FDPIC would
Define an ARM-specific version of elf_is_fdpic:
FDPIC ELF objects are identified with e_ident[EI_OSABI] ==
ELFOSABI_ARM_FDPIC.
Co-Authored-By: Mickaël Guêné
Signed-off-by: Christophe Lyon
diff --git a/include/elf.h b/include/elf.h
index c0dc9bb..934dbbd 100644
--- a/include/elf.h
+++ b/include/
Add FDPIC info into image_info structure since interpreter info is on
stack and needs to be saved to be accessed later on.
Co-Authored-By: Mickaël Guêné
Signed-off-by: Christophe Lyon
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
index 76d7718..1ee1e38 100644
--- a/linux-user/elfloa
The .INS config files can normally be found on CD-ROM ISO images,
so by supporting these files, it is now possible to boot directly
when the TFTP server is set up with the contents of such an CD-ROM
image.
Signed-off-by: Thomas Huth
---
pc-bios/s390-ccw/netmain.c | 51 +++
Since it is quite cumbersome to manually create a combined kernel with
initrd image for network booting, we now support loading via pxelinux
configuration files, too. In these files, the kernel, initrd and command
line parameters can be specified seperately, and the firmware then takes
care of glue
When we want to support pxelinux-style network booting later, we've got
to do several TFTP transfers - and we do not want to apply for a new IP
address via DHCP each time. So split up net_load into three parts:
1. net_init(), which initializes virtio-net, gets an IP address via DHCP
and prints
Some patches to improve the network boot experience on s390x:
First patch is just a minor code refactoring which should not have
any visible impact, but makes the following patches easier.
Patch 2 and 3 add support for loading kernels via configuration files,
pxelinux-style and .INS-file style. T
The netboot firmware so far simply jumped directly into the OS kernel
after the download has been completed. This, however, bears the risk
that the virtio-net device still might be active in the background and
incoming packets are still placed into the buffers - which could destroy
memory of the no
On 04/23/2018 08:46 AM, David Gibson wrote:
> On Thu, Apr 19, 2018 at 02:42:59PM +0200, Cédric Le Goater wrote:
>> The XiveFabric offers a simple interface, between the XiveSourve
>> object and the device model owning the interrupt sources, to forward
>> an event notification to the XIVE interrupt
David Gibson writes:
> On Mon, Apr 23, 2018 at 11:43:02AM +0530, Nikunj A Dadhania wrote:
>> Set the newly added register(KVM_REG_PPC_ONLINE) to indicate if the vcpu is
>> online(1) or offline(0)
>>
>> KVM will use this information to set the RWMR register, which controls the
>> PURR
>> and SPU
Hi,
I was trying to run qemu with spdk, referring to http://www.spdk.io/doc/
vhost.html#vhost_qemu_config . Steps were strictly followed.
# Environment: latest CentOS 7 kernel, nvme ssd, spdk v18.01.x,
> dpdk 17.11.1, qemu 2.11.1
cd spdk
> sudo su
> ulimit -l unlimited
> HUGEMEM=2048 ./scripts
vfio display needs to release the invalid display resource and disable
the scanout mode during guest OS reboot, otherwise bugs come out.
Thanks hang.y...@intel.com for helping root cause the issue.
Tina Zhang (2):
console: introduce dpy_gfx_switch_surface
ui: introduce vfio_display_reset
hw
During guest OS reboot, guest framebuffer is invalid. It will cause
bugs, if the invalid guest framebuffer is still used by host.
This patch is to introduce vfio_display_reset which is invoked
during vfio display reset. This vfio_display_reset function is used
to release the invalid display resour
dpy_gfx_switch_surface is used to ask each valid DisplayChangeListener
of a QemuConsole to switch to another DisplaySurface.
Signed-off-by: Tina Zhang
---
include/ui/console.h | 2 ++
ui/console.c | 16
2 files changed, 18 insertions(+)
diff --git a/include/ui/console.
On Fri, 2018-04-20 at 20:21 +1000, David Gibson wrote:
> On Fri, Apr 20, 2018 at 11:31:10AM +0200, Andrea Bolognani wrote:
> > I'll check out what other distros are doing: if all the major ones
> > are defaulting to 64 KiB pages these days, it might be reasonable
> > to do the same and pretend smal
When resume of a stopped guest immediately runs into block device
errors, the BLOCK_IO_ERROR event is sent before the RESUME event.
Reproducer:
1. Create a scratch image
$ dd if=/dev/zero of=scratch.img bs=1M count=100
Size doesn't actually matter.
2. Prepare blkdebug configuration:
$
On 23 April 2018 at 04:31, Thomas Huth wrote:
> On 21.04.2018 11:27, Mike R wrote:
>> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to
>> qemu-devel@nongnu.org
>>
>> reported.
>
> Well, please also report:
It's kind of our own fault that we didn't ask for those
sorts of details
On 23 April 2018 at 07:40, Cédric Le Goater wrote:
> commit 1d3e65aa7ac5 ("hw/timer: Add value matching support to
> aspeed_timer") increased the vmstate version of the timers array but
> doing so, it broke migration. To fix, we also need to change the
> vmstate version of the aspeed timer control
2018-04-21 1:34 GMT+08:00 John Snow :
>
>
> On 04/20/2018 07:13 AM, Bob Chen wrote:
> > 2.11.1 could work, qemu is no longer occupying 100% CPU. That's
> > interesting...
> >
>
> Does 2.12 use 100% even at the firmware menu? Maybe we're not giving
> this VM long enough to hit the spot that causes
On 04/23/2018 11:12 AM, Peter Maydell wrote:
>> diff --git a/hw/timer/aspeed_timer.c b/hw/timer/aspeed_timer.c
>> index 50acbf530a3a..7df19bd9df91 100644
>> --- a/hw/timer/aspeed_timer.c
>> +++ b/hw/timer/aspeed_timer.c
>> @@ -498,8 +498,8 @@ static const VMStateDescription vmstate_aspeed_timer = {
On 04/19/2018 03:10 PM, Gerd Hoffmann wrote:
If some event caused some larger playback hickup the fine-grained timer
adjust isn't able to recover. Use a buffer overruns and underruns as
indicator for that. Reset timer adjust logic in case we detected one.
It seems that this patch causes big
On Sun, Apr 22, 2018 at 09:37:52PM -0400, Simon Marchi wrote:
> On 2018-04-09 10:08 PM, Stefan Hajnoczi wrote:
> > I wonder what the point of select-frame is then...
> >
> > I have CCed the GDB mailing list. Maybe someone can help us. Context:
> >
> > QEMU implements coroutines using jmpbuf. W
On 23 April 2018 at 10:28, Cédric Le Goater wrote:
> On 04/23/2018 11:12 AM, Peter Maydell wrote:
>>> diff --git a/hw/timer/aspeed_timer.c b/hw/timer/aspeed_timer.c
>>> index 50acbf530a3a..7df19bd9df91 100644
>>> --- a/hw/timer/aspeed_timer.c
>>> +++ b/hw/timer/aspeed_timer.c
>>> @@ -498,8 +498,8
On 23.04.2018 05:28, David Gibson wrote:
> On Fri, Apr 20, 2018 at 02:34:55PM +0200, David Hildenbrand wrote:
>> Let's allow to query the MemoryHotplugState from the machine.
>>
>> This allows us to generically detect if a certain machine has support
>> for memory devices, and to generically manage
On Mon, Apr 23, 2018 at 10:10:10AM +1000, David Gibson wrote:
> On Fri, Apr 20, 2018 at 10:34:57AM +0100, Daniel P. Berrangé wrote:
> > On Fri, Apr 20, 2018 at 10:11:08AM +0200, Laszlo Ersek wrote:
> > > On 04/19/18 11:12, Daniel P. Berrangé wrote:
> > > > On Thu, Apr 19, 2018 at 10:39:32AM +0200,
On Mon, Apr 23, 2018 at 10:10:47AM +0100, Peter Maydell wrote:
> On 23 April 2018 at 04:31, Thomas Huth wrote:
> > On 21.04.2018 11:27, Mike R wrote:
> >> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to
> >> qemu-devel@nongnu.org
> >>
> >> reported.
> >
> > Well, please also rep
On Mon, Apr 23, 2018 at 05:31:28AM +0200, Thomas Huth wrote:
> On 21.04.2018 11:27, Mike R wrote:
> > (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to
> > qemu-devel@nongnu.org
> >
> > reported.
>
> Well, please also report:
>
> - Which version of QEMU are you using?
>
> - Whi
23.04.2018 12:33, Stefan Hajnoczi wrote:
On Sun, Apr 22, 2018 at 09:37:52PM -0400, Simon Marchi wrote:
On 2018-04-09 10:08 PM, Stefan Hajnoczi wrote:
I wonder what the point of select-frame is then...
I have CCed the GDB mailing list. Maybe someone can help us. Context:
QEMU implements coro
Laszlo Ersek writes:
> Now that we have @SysEmuTarget, it makes sense to restict
> @TargetInfo.@arch to valid sysemu targets at the schema level.
We could mention that supported targets become visible in QMP
introspection. But I can't see what QMP clients could do with this
information, so let'
On Fri, 20 Apr 2018 08:31:18 +0200
Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > On Thu, Apr 19, 2018 at 10:00:04AM +0200, Igor Mammedov wrote:
> >> On Wed, 18 Apr 2018 09:08:30 +0200
> >> Markus Armbruster wrote:
> >>
> >> > Eduardo Habkost writes:
> >> >
> >> > > On Tue,
Laszlo Ersek writes:
> We'll soon need an enumeration type that lists all the softmmu targets
> that QEMU (the project) supports. Introduce @SysEmuTarget to
> "common.json".
>
> Cc: "Daniel P. Berrange"
> Cc: David Gibson
> Cc: Eric Blake
> Cc: Gerd Hoffmann
> Cc: Kashyap Chamarthy
> Cc: Mar
On 22.04.2018 12:10, David Gibson wrote:
> On Sun, Apr 22, 2018 at 10:21:34AM +0200, David Hildenbrand wrote:
>> On 22.04.2018 06:26, David Gibson wrote:
>>> On Fri, Apr 20, 2018 at 02:34:54PM +0200, David Hildenbrand wrote:
On the qmp level, we already have the concept of memory devices:
On 04/23/2018 11:34 AM, Peter Maydell wrote:
> On 23 April 2018 at 10:28, Cédric Le Goater wrote:
>> On 04/23/2018 11:12 AM, Peter Maydell wrote:
diff --git a/hw/timer/aspeed_timer.c b/hw/timer/aspeed_timer.c
index 50acbf530a3a..7df19bd9df91 100644
--- a/hw/timer/aspeed_timer.c
On 04/23/2018 11:34 AM, Peter Maydell wrote:
> On 23 April 2018 at 10:28, Cédric Le Goater wrote:
>> On 04/23/2018 11:12 AM, Peter Maydell wrote:
diff --git a/hw/timer/aspeed_timer.c b/hw/timer/aspeed_timer.c
index 50acbf530a3a..7df19bd9df91 100644
--- a/hw/timer/aspeed_timer.c
On Mon, 16 Apr 2018 09:45:20 +0200
Thomas Huth wrote:
> "size_t" should be an unsigned type according to the C standard.
> Thus we should also use this convention in the s390-ccw firmware to avoid
> confusion. I checked the sources, and apart from one spot in libc.c, the
> code should all be fine
commit 1d3e65aa7ac5 ("hw/timer: Add value matching support to
aspeed_timer") increased the vmstate version of aspeed.timer because
the state had changed, but it also bumped the version of the
VMSTATE_STRUCT_ARRAY under the aspeed.timerctrl which did not need to.
Change back this version to fix mig
Problem solved. Got a reply from Intel just now.
-- Forwarded message --
From: Liu, Changpeng
Date: 2018-04-23 18:06 GMT+08:00
Subject: [Qemu-devel] [QEMU + SPDK] The demo in the official document is
not working
To: "a175818...@gmail.com"
Hi Bob,
The issues was introduced by
This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
containing Windows crashdump header, which can help to convert to a valid
WinDbg-understandable crashdump file, or immediately create such file.
The crashdump will be obtained by joining physical memory dump and 8K header
e
On 23 April 2018 at 11:14, Cédric Le Goater wrote:
> commit 1d3e65aa7ac5 ("hw/timer: Add value matching support to
> aspeed_timer") increased the vmstate version of aspeed.timer because
> the state had changed, but it also bumped the version of the
> VMSTATE_STRUCT_ARRAY under the aspeed.timerctrl
On 20/04/2018 20:35, Emilio G. Cota wrote:
> The executable is now larger:
>
> - before:
>textdata bss dec hex filename
> 9864951 2944592 4371560 1718110310629af
> aarch64-softmmu/qemu-system-aarch64
>
> - after:
>textdata bss dec hex filename
> 98
On 20 April 2018 at 18:26, francisco iglesias wrote:
>
>
> On 19 April 2018 at 08:27, Sai Pavan Boddu
> wrote:
>>
>> SNOOP_NONE state handle is moved above in the if ladder, as it's same
>> as SNOOP_STRIPPING during data cycles.
>>
>> Signed-off-by: Sai Pavan Boddu
>
>
> Reviewed-by: Francisco I
On Thu, 12 Apr 2018 21:26:02 +0200
David Hildenbrand wrote:
> Calling pause_all_vcpus()/resume_all_vcpus() from a VCPU thread might
> not be the best idea. As pause_all_vcpus() temporarily drops the qemu
> mutex, two parallel calls to pause_all_vcpus() can be active at a time,
> resulting in a de
On Wed, 18 Apr 2018 16:33:13 +0200
David Hildenbrand wrote:
> > static void s390_ipl_class_init(ObjectClass *klass, void *data)
> > diff --git a/hw/s390x/ipl.h b/hw/s390x/ipl.h
> > index 0570d0ad75..102f1ea7af 100644
> > --- a/hw/s390x/ipl.h
> > +++ b/hw/s390x/ipl.h
> > @@ -87,7 +87,17 @@ int s3
* Cédric Le Goater (c...@kaod.org) wrote:
> On 04/23/2018 11:34 AM, Peter Maydell wrote:
> > On 23 April 2018 at 10:28, Cédric Le Goater wrote:
> >> On 04/23/2018 11:12 AM, Peter Maydell wrote:
> diff --git a/hw/timer/aspeed_timer.c b/hw/timer/aspeed_timer.c
> index 50acbf530a3a..7df19bd
On Mon, Apr 23, 2018 at 11:36:48AM +0200, David Hildenbrand wrote:
> On 23.04.2018 05:28, David Gibson wrote:
> > On Fri, Apr 20, 2018 at 02:34:55PM +0200, David Hildenbrand wrote:
> >> Let's allow to query the MemoryHotplugState from the machine.
> >>
> >> This allows us to generically detect if a
On 23.04.2018 12:44, David Gibson wrote:
> On Mon, Apr 23, 2018 at 11:36:48AM +0200, David Hildenbrand wrote:
>> On 23.04.2018 05:28, David Gibson wrote:
>>> On Fri, Apr 20, 2018 at 02:34:55PM +0200, David Hildenbrand wrote:
Let's allow to query the MemoryHotplugState from the machine.
>>
On 04/23/2018 12:29 PM, Peter Maydell wrote:
> On 23 April 2018 at 11:14, Cédric Le Goater wrote:
>> commit 1d3e65aa7ac5 ("hw/timer: Add value matching support to
>> aspeed_timer") increased the vmstate version of aspeed.timer because
>> the state had changed, but it also bumped the version of the
>>> I think it's nice to at least do the "bump version" thing, so you
>>> get a (hopefully comprehensible) error rather than just wrong
>>> data if you do try a cross version migration,
>>
>> On that topic, the error message was :
>>
>> Missing section footer for aspeed.timerctrl
>>
>> which
On 23.04.2018 12:08, Cornelia Huck wrote:
> On Mon, 16 Apr 2018 09:45:20 +0200
> Thomas Huth wrote:
>
>> "size_t" should be an unsigned type according to the C standard.
>> Thus we should also use this convention in the s390-ccw firmware to avoid
>> confusion. I checked the sources, and apart fro
Hi Peter,
On 04/16/2018 02:59 PM, Peter Maydell wrote:
> On 12 April 2018 at 08:37, Eric Auger wrote:
>> This patch implements the page table walk for VMSAv8-64.
>>
>> Signed-off-by: Eric Auger
>> Signed-off-by: Prem Mallappa
>
>> diff --git a/hw/arm/smmu-common.c b/hw/arm/smmu-common.c
>> ind
On 23/04/2018 10:45, Markus Armbruster wrote:
> When resume of a stopped guest immediately runs into block device
> errors, the BLOCK_IO_ERROR event is sent before the RESUME event.
>
> Reproducer:
>
> 1. Create a scratch image
>$ dd if=/dev/zero of=scratch.img bs=1M count=100
>
>Size do
On 23 April 2018 at 08:51, Christophe Lyon wrote:
> Define an ARM-specific version of elf_is_fdpic:
> FDPIC ELF objects are identified with e_ident[EI_OSABI] ==
> ELFOSABI_ARM_FDPIC.
>
> Co-Authored-By: Mickaël Guêné
> Signed-off-by: Christophe Lyon
>
> diff --git a/include/elf.h b/include/elf.h
On Fri, 20 Apr 2018 14:34:56 +0200
David Hildenbrand wrote:
> To be able to reuse MemoryDevice logic from other devices besides
> pc-dimm, factor the relevant stuff out into the MemoryDevice code.
>
> As we don't care about slots for memory devices that are not pc-dimm,
> don't factor that part
On 23 April 2018 at 08:51, Christophe Lyon wrote:
> We want to avoid code disabled by default, because it ends up less
> tested. This patch removes all instances of #ifdef CONFIG_USE_FDPIC,
> most of which can be safely kept. For the ones that should be
> conditionally executed, we define elf_is_f
On Fri, 20 Apr 2018 14:34:53 +0200
David Hildenbrand wrote:
> Right now we can only map PCDIMM/NVDIMM into guest address space. In the
> future, we might want to do the same for virtio devices - e.g.
> virtio-pmem or virtio-mem. Especially, they should be able to live side
> by side to each other
From: "Edgar E. Iglesias"
Hi,
This is a series of fixes for bugs I ran into when adding support
for extended addressing. It would be nice to get these into 2.12
if it's not too late.
Cheers,
Edgar
ChangeLog:
v1 -> v2:
* Corrected fix making MSR.PVR read-only.
Edgar E. Iglesias (5):
target-
From: "Edgar E. Iglesias"
Do not clobber the IMM register on reversed load/stores.
Signed-off-by: Edgar E. Iglesias
---
target/microblaze/translate.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/target/microblaze/translate.c b/target/microblaze/translate.c
index ec12fed49d..100883e2cc
From: "Edgar E. Iglesias"
Fix trap checks for FPU insns when extended FPU insns are enabled.
Reviewed-by: Alistair Francis
Signed-off-by: Edgar E. Iglesias
---
target/microblaze/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/microblaze/translate.c b/tar
From: "Edgar E. Iglesias"
Respect MSR.PVR as read-only. We were wrongly overwriting the PVR bit.
Signed-off-by: Edgar E. Iglesias
---
target/microblaze/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/microblaze/translate.c b/target/microblaze/translate.c
From: "Edgar E. Iglesias"
Make the TLBX MISS bit read-only.
Reviewed-by: Alistair Francis
Signed-off-by: Edgar E. Iglesias
---
target/microblaze/mmu.c | 4
1 file changed, 4 insertions(+)
diff --git a/target/microblaze/mmu.c b/target/microblaze/mmu.c
index 8391811900..9d5e6aa8a5 100644
From: "Edgar E. Iglesias"
Make TLBSX write-only and guest-error log reads from it.
Reviewed-by: Alistair Francis
Signed-off-by: Edgar E. Iglesias
---
target/microblaze/mmu.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/microblaze/mmu.c b/target/microblaze/mmu
On 23.04.2018 14:19, Igor Mammedov wrote:
> On Fri, 20 Apr 2018 14:34:56 +0200
> David Hildenbrand wrote:
>
>> To be able to reuse MemoryDevice logic from other devices besides
>> pc-dimm, factor the relevant stuff out into the MemoryDevice code.
>>
>> As we don't care about slots for memory devi
Hi Peter,
On 04/16/2018 03:08 PM, Peter Maydell wrote:
> On 12 April 2018 at 08:37, Eric Auger wrote:
>> From: Prem Mallappa
>>
>> This patch implements a skeleton for the smmuv3 device.
>> Datatypes and register definitions are introduced. The MMIO
>> region, the interrupts and the queue are ini
On 23.04.2018 14:31, Igor Mammedov wrote:
> On Fri, 20 Apr 2018 14:34:53 +0200
> David Hildenbrand wrote:
>
>> Right now we can only map PCDIMM/NVDIMM into guest address space. In the
>> future, we might want to do the same for virtio devices - e.g.
>> virtio-pmem or virtio-mem. Especially, they
On 23 April 2018 at 08:51, Christophe Lyon wrote:
> Add FDPIC info into image_info structure since interpreter info is on
> stack and needs to be saved to be accessed later on.
>
> Co-Authored-By: Mickaël Guêné
> Signed-off-by: Christophe Lyon
>
> diff --git a/linux-user/elfload.c b/linux-user/
>
>> +/* we will need a new memory slot for kvm and vhost */
>> +if (kvm_enabled() && !kvm_has_free_slot(machine)) {
>> +error_setg(errp, "hypervisor has no free memory slots left");
>> +return;
>> +}
>> +if (!vhost_has_free_slot()) {
>> +error_setg(errp, "
Richard Henderson writes:
> On 04/19/2018 03:58 AM, Alex Bennée wrote:
>> What would be really
>> helpful is if the respective maintainers could encode their EXACT
>> STEPS for building their cross compilers into some docker recipes.
>
> I've just re-built my alphaev67 cross-environment and reco
On 23/04/2018 14:17, Peter Maydell wrote:
On 23 April 2018 at 08:51, Christophe Lyon wrote:
Define an ARM-specific version of elf_is_fdpic:
FDPIC ELF objects are identified with e_ident[EI_OSABI] ==
ELFOSABI_ARM_FDPIC.
Co-Authored-By: Mickaël Guêné
Signed-off-by: Christophe Lyon
diff --git
Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben:
> When resume of a stopped guest immediately runs into block device
> errors, the BLOCK_IO_ERROR event is sent before the RESUME event.
>
> Reproducer:
>
> 1. Create a scratch image
>$ dd if=/dev/zero of=scratch.img bs=1M count=100
>
Hi,
> void dpy_gfx_replace_surface(QemuConsole *con,
> DisplaySurface *surface);
> +void dpy_gfx_switch_surface(QemuConsole *con,
> + DisplaySurface *surface);
Why? Any problems with dpy_gfx_replace_surface?
cheers,
Gerd
On Fri, Apr 20, 2018 at 02:45:31PM +0800, Su Hang wrote:
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index 26184bcd7c26..898a7af114ea 100644
> --- a/hw/arm/boot.c
> +++ b/hw/arm/boot.c
> @@ -1070,12 +1070,20 @@ static void arm_load_kernel_notify(Notifier
> *notifier, void *data)
> kern
On 23 April 2018 at 08:51, Christophe Lyon wrote:
> The FDPIC restorer needs to deal with a function descriptor, hence we
> have to extend 'retcode' such that it can hold the instructions needed
> to perform this.
>
> The restorer sequence uses the same thumbness as the exception
> handler (mainly
On Mon, Apr 23, 2018 at 11:50:16AM +0200, Igor Mammedov wrote:
> On Fri, 20 Apr 2018 08:31:18 +0200
> Markus Armbruster wrote:
>
> > Eduardo Habkost writes:
> >
> > > On Thu, Apr 19, 2018 at 10:00:04AM +0200, Igor Mammedov wrote:
> > >> On Wed, 18 Apr 2018 09:08:30 +0200
> > >> Markus Armbrus
> +surface = qemu_console_surface(vdev->dpy->con);
> +dpy_gl_scanout_disable(vdev->dpy->con);
> +dpy_gfx_switch_surface(vdev->dpy->con, surface);
Hmm, so you ask which surface is active, then switch to it.
Why?
Maybe you just need a full display update after disabling the gl
scanout?
On 23 April 2018 at 06:18, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This allows to pin the host controller in the Linux PCI domain space.
> Linux requires that property to be available consistently or not at all,
> in which case the domain number becomes unstable on additions/removals.
> Adding i
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/20/2018 12:57 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Update the migration docs:
> >
> > Among other changes:
> > * Added a general list of advice for device authors
> > * Reordered the section on cond
On Sat 21 Apr 2018 12:09:10 AM CEST, Max Reitz wrote:
> Currently we do not take permissions on a file while it is being
> created. That is a bit sad. The simplest way to test this is the
> following:
>
> $ qemu-img create -f qcow2 foo.qcow2 64M
> Formatting 'foo.qcow2', fmt=qcow2 size=67
On 23 April 2018 at 13:53, Christophe Lyon wrote:
> On 23/04/2018 14:17, Peter Maydell wrote:
>> I have a strong dislike for per-target ifdef ladders. Can we instead
>> put the target's implementation of elf_is_fdpic() into
>> linux-user/$ARCH/target_elf.h
>> and also have that header do
>> #defin
On 04/23/2018 02:37 AM, Simon Marchi wrote:
> On 2018-04-09 10:08 PM, Stefan Hajnoczi wrote:
>> I wonder what the point of select-frame is then...
>>
>> I have CCed the GDB mailing list. Maybe someone can help us. Context:
>>
>> QEMU implements coroutines using jmpbuf. We'd like to print corouti
This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
containing Windows crashdump header, which can help to convert to a valid
WinDbg-understandable crashdump file, or immediately create such file.
The crashdump will be obtained by joining physical memory dump and 8K header
e
On 04/23/2018 12:16 AM, David Gibson wrote:
> On Sun, Apr 22, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
>> On 21 April 2018 at 22:16, Philippe Mathieu-Daudé wrote:
>>> This fixes the following ASan warning:
>>>
>>> $ mips64el-softmmu/qemu-system-mips64el -M boston -kernel vmlinux.gz.itb
>>
On 23 April 2018 at 13:10, Auger Eric wrote:
> Hi Peter,
>
> On 04/16/2018 02:59 PM, Peter Maydell wrote:
>> On 12 April 2018 at 08:37, Eric Auger wrote:
>>> +/**
>>> + * TODO: handle the case where the level resolves less than
>>> + * granule_sz -3 IA bits.
>>> + */
>>> +static inline
>>> +uint
On 23 April 2018 at 14:57, Philippe Mathieu-Daudé wrote:
> On 04/23/2018 12:16 AM, David Gibson wrote:
>> On Sun, Apr 22, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
>>> If we need to do an unaligned load, then ldl_p() is the
>>> right way to do it. (We could also just do
>>> *addr = ldl_be_p(
On 23/04/2018 14:49, Peter Maydell wrote:
On 23 April 2018 at 08:51, Christophe Lyon wrote:
Add FDPIC info into image_info structure since interpreter info is on
stack and needs to be saved to be accessed later on.
Co-Authored-By: Mickaël Guêné
Signed-off-by: Christophe Lyon
diff --git a/l
This fixes the following ASan warning:
$ mips64el-softmmu/qemu-system-mips64el -M boston -kernel vmlinux.gz.itb
-nographic
hw/core/loader-fit.c:108:17: runtime error: load of misaligned address
0x7f95cd7e4264 for type 'fdt64_t', which requires 8 byte alignment
0x7f95cd7e4264: note: pointer
On 04/23/2018 11:04 AM, Peter Maydell wrote:
> On 23 April 2018 at 14:57, Philippe Mathieu-Daudé wrote:
>> On 04/23/2018 12:16 AM, David Gibson wrote:
>>> On Sun, Apr 22, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
If we need to do an unaligned load, then ldl_p() is the
right way to d
On 23/04/2018 15:05, Peter Maydell wrote:
On 23 April 2018 at 08:51, Christophe Lyon wrote:
The FDPIC restorer needs to deal with a function descriptor, hence we
have to extend 'retcode' such that it can hold the instructions needed
to perform this.
The restorer sequence uses the same thumbnes
> On 04/23/2018 11:04 AM, Peter Maydell wrote:
>> On 23 April 2018 at 14:57, Philippe Mathieu-Daudé wrote:
>>> On 04/23/2018 12:16 AM, David Gibson wrote:
On Sun, Apr 22, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
> If we need to do an unaligned load, then ldl_p() is the
> right w
Alex Bennée writes:
> Richard Henderson writes:
>
>> On 04/19/2018 03:58 AM, Alex Bennée wrote:
>>> What would be really
>>> helpful is if the respective maintainers could encode their EXACT
>>> STEPS for building their cross compilers into some docker recipes.
>>
>> I've just re-built my alpha
On Thu, Apr 19, 2018 at 05:45:08PM +0100, Ian Jackson wrote:
> We need to restrict *all* the control fds that qemu opens. Looking in
> /proc/PID/fd shows there are many; their allocation seems scattered
> throughout Xen support code in qemu.
>
> We must postpone the restrict call until roughly th
On 23.04.2018 14:19, Igor Mammedov wrote:
> On Fri, 20 Apr 2018 14:34:56 +0200
> David Hildenbrand wrote:
>
>> To be able to reuse MemoryDevice logic from other devices besides
>> pc-dimm, factor the relevant stuff out into the MemoryDevice code.
>>
>> As we don't care about slots for memory devi
This image is not enough to cross-build QEMU,
but it is useful enough to cross-compile TCG tests.
Suggested-by: Alex Bennée
Signed-off-by: Philippe Mathieu-Daudé
---
tests/docker/dockerfiles/debian-alpha-cross.docker | 13 +
1 file changed, 13 insertions(+)
create mode 100644 tests
With the STSI instruction, we can get the UUID of the current VM instance,
so we can support loading pxelinux config files via UUID in the file name,
too.
Signed-off-by: Thomas Huth
---
Sorry, just found out how to get the VM UUID after sending out the v2
series, so this is now patch 5 of 4 ;-)
On Thu, Apr 19, 2018 at 05:45:06PM +0100, Ian Jackson wrote:
> From: Anthony PERARD
>
> Xen libraries in 4.10 include a new xentoolcore library. This
> contains the xentoolcore_restrict_all function which we are about to
> want to use.
>
> Signed-off-by: Ian Jackson
> Acked-by: Stefano Stabell
1 - 100 of 211 matches
Mail list logo
