On Thu, Apr 21, 2016 at 10:22:10AM -0700, Jianjun Duan wrote:
>
>
> On 04/19/2016 10:14 PM, David Gibson wrote:
> >On Fri, Apr 15, 2016 at 01:33:04PM -0700, Jianjun Duan wrote:
> >>ccs_list in spapr state maintains the device tree related
> >>information on the rtas side for hotplugged devices.
On Thu, Apr 21, 2016 at 04:01:16PM +1000, Alexey Kardashevskiy wrote:
> On 04/20/2016 12:33 PM, David Gibson wrote:
> >A number of guests supported by qemu use IEEE12750 (Open Firmware)
> >style device trees for hardware discovery. In some cases (mac99,
> >pseries) they get this device tree via
On Thu, Apr 21, 2016 at 04:03:12PM +1000, Alexey Kardashevskiy wrote:
> On 04/21/2016 03:52 PM, David Gibson wrote:
> >On Thu, Apr 21, 2016 at 03:14:48PM +1000, Alexey Kardashevskiy wrote:
> >>On 04/20/2016 12:33 PM, David Gibson wrote:
> >>>The flattened device tree passed to pseries guests
On Thu, Apr 21, 2016 at 10:03:56AM -0700, Jianjun Duan wrote:
>
>
> On 04/19/2016 09:32 PM, David Gibson wrote:
> >On Fri, Apr 15, 2016 at 01:33:02PM -0700, Jianjun Duan wrote:
> >>To manage hotplug/unplug of dynamic resources such as PCI cards,
> >>memory, and CPU on sPAPR guests, a firmware
> I wonder if QEMU or the guest (BIOS? Kernel?) is zeroing the memory ? For
> normal memory I'd expect it to zero it.
Zeroing page probably happens when allocating memory, I am not sure if it did
happen once release the page. And, I am trying to find specific pattern of the
content I write
> On Wed, Apr 20, 2016 at 01:41:24AM +, Li, Liang Z wrote:
> > > Cc: Rik van Riel; v...@zeniv.linux.org.uk;
> > > linux-ker...@vger.kernel.org; quint...@redhat.com;
> > > amit.s...@redhat.com; pbonz...@redhat.com; dgilb...@redhat.com;
> > > linux...@kvack.org; k...@vger.kernel.org; qemu-
On Thu, 04/21 17:54, Lutz Vieweg wrote:
> Nevertheless, I think qemu could be somewhat more verbose, reporting
> when and why it stops emulation. Something like a message to the monitor
> or to standard out would be helpful to start with...
QEMU does report an error message to connected monitor
Hi Stefan,
> From: Stefan Hajnoczi [mailto:stefa...@redhat.com]
> Sent: Thursday, April 21, 2016 11:24 PM
> Subject: Re: [RFC v3] virtio-crypto specification
>
> On Tue, Apr 19, 2016 at 08:37:13AM +, Gonglei (Arei) wrote:
> > 1.6.1.1 Driver Requirements: Session operation
> > The driver MUST
This is a first attempt at making tb_flush not have to stop all CPUs.
There are issues as pointed out below, but this could be a good start.
Context:
https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg04658.html
https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg06942.html
Known
The setting of tcg_ctx.code_gen_buffer_size is done by the only caller of
size_code_gen_buffer(), which is code_gen_alloc():
$ git grep size_code_gen_buffer
translate-all.c:static inline size_t size_code_gen_buffer(size_t tb_size)
translate-all.c:tcg_ctx.code_gen_buffer_size =
Signed-off-by: Emilio G. Cota
---
translate-all.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/translate-all.c b/translate-all.c
index e700399..bba9b62 100644
--- a/translate-all.c
+++ b/translate-all.c
@@ -668,39 +668,39 @@ static inline void
On 04/21/16 18:23, Christoffer Dall wrote:
> Hi,
>
> Commit 9fac18f (oslib: allocate PROT_NONE pages on top of RAM,
> 2015-09-10) had the unfortunate side effect that memory slots registered
> with KVM no longer contain a userspace address that is aligned to a 2M
> boundary, causing the use of
Sergey Fedorov writes:
> On 21/04/16 19:16, Sergey Fedorov wrote:
>> On 21/04/16 18:55, Alex Bennée wrote:
>>> Sergey Fedorov writes:
>>>
On 18/04/16 20:51, Sergey Fedorov wrote:
> On 18/04/16 20:17, Alex Bennée wrote:
>> Sergey Fedorov
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fourth release candidate for the QEMU 2.6 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.6.0-rc3.tar.bz2
A note from the
On 21.04.16 18:23, Christoffer Dall wrote:
> Hi,
>
> Commit 9fac18f (oslib: allocate PROT_NONE pages on top of RAM,
> 2015-09-10) had the unfortunate side effect that memory slots registered
> with KVM no longer contain a userspace address that is aligned to a 2M
> boundary, causing the use of
From: Janne Karhunen
Vmdk images have metadata to indicate the vmware virtual
hardware version image was created/tested to run with.
Allow users to specify that version via new 'hwversion'
option.
Signed-off-by: Janne Karhunen
---
Hi Andrea,
I'm wondering if this bug is the opposite way around from what I originally
thought it was - I don't think the problem is 0 pages on the destination; I
think
it's more subtle.
I added some debug to print the source VMs memory and also
the byte in the destination's 1st page (this is
On 21/04/16 20:49, Alex Bennée wrote:
> Sergey Fedorov writes:
>
>> On 18/04/16 18:47, Sergey Fedorov wrote:
>>> On 18/04/16 18:34, Cornelia Huck wrote:
On Mon, 18 Apr 2016 16:51:16 +0200
Cornelia Huck wrote:
> On Thu, 7 Apr
The new autoconverge throttling commands have been tested for a release now. It
is time to move them out of the experimental state.
Signed-off-by: Jason J. Herne
---
hmp.c | 28 +-
migration/migration.c | 56
Sergey Fedorov writes:
> On 18/04/16 18:47, Sergey Fedorov wrote:
>> On 18/04/16 18:34, Cornelia Huck wrote:
>>> On Mon, 18 Apr 2016 16:51:16 +0200
>>> Cornelia Huck wrote:
>>>
On Thu, 7 Apr 2016 18:53:44 +0300
Sergey Fedorov
On 18/04/16 18:47, Sergey Fedorov wrote:
> On 18/04/16 18:34, Cornelia Huck wrote:
>> On Mon, 18 Apr 2016 16:51:16 +0200
>> Cornelia Huck wrote:
>>
>>> On Thu, 7 Apr 2016 18:53:44 +0300
>>> Sergey Fedorov wrote:
>>>
From: Sergey Fedorov
On 04/19/2016 10:14 PM, David Gibson wrote:
On Fri, Apr 15, 2016 at 01:33:04PM -0700, Jianjun Duan wrote:
ccs_list in spapr state maintains the device tree related
information on the rtas side for hotplugged devices. In racing
situations between hotplug events and migration operation, a rtas
On 21/04/16 19:16, Sergey Fedorov wrote:
> On 21/04/16 18:55, Alex Bennée wrote:
>> Sergey Fedorov writes:
>>
>>> On 18/04/16 20:51, Sergey Fedorov wrote:
On 18/04/16 20:17, Alex Bennée wrote:
> Sergey Fedorov writes:
>> On 18/04/16 17:09,
On 04/19/2016 09:32 PM, David Gibson wrote:
On Fri, Apr 15, 2016 at 01:33:02PM -0700, Jianjun Duan wrote:
To manage hotplug/unplug of dynamic resources such as PCI cards,
memory, and CPU on sPAPR guests, a firmware abstraction known as
a Dynamic Resource Connector (DRC) is used to assign a
[adding qemu]
On 04/21/2016 10:31 AM, Alex Bligh wrote:
>
> On 21 Apr 2016, at 16:45, Wouter Verhelst wrote:
>
>> On Thu, Apr 21, 2016 at 03:21:45PM +0100, Alex Bligh wrote:
>>> The website on sourceforge was looking a bit tired.
>>>
>>> I moved it over to github pages (currently
On 04/19/2016 09:30 PM, David Gibson wrote:
On Fri, Apr 15, 2016 at 01:33:01PM -0700, Jianjun Duan wrote:
There are possible racing situations involving hotplug events and
guest migration. For cases where a hotplug event is migrated, or
the guest is in the process of fetching device tree at
On Thu, 04/21 10:04, Fam Zheng wrote:
> This ensures the bdrv_drained_begin() in block layer is effective and
> fixes launchpad bug #1570134.
>
> Signed-off-by: Fam Zheng
> ---
> hw/virtio/virtio.c | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git
On 21 April 2016 at 15:42, Eric Blake wrote:
> The NBD protocol does not (yet) force any alignment constraints
> on clients. Even though qemu NBD clients always send requests
> that are aligned to 512 bytes, we must be prepared for non-qemu
> clients that don't care about
On Wed, Apr 20, 2016 at 12:39:45 -0700, Richard Henderson wrote:
> On 04/20/2016 11:11 AM, Emilio G. Cota wrote:
> >On Wed, Apr 20, 2016 at 10:55:45 -0700, Richard Henderson wrote:
> >>On 04/20/2016 10:17 AM, Emilio G. Cota wrote:
(snip)
> >My comment was related to this:
> >
> >>[...] do note
Hi,
Commit 9fac18f (oslib: allocate PROT_NONE pages on top of RAM,
2015-09-10) had the unfortunate side effect that memory slots registered
with KVM no longer contain a userspace address that is aligned to a 2M
boundary, causing the use of THP to fail in the kernel.
I fail to see where in the
On 21/04/16 18:55, Alex Bennée wrote:
> Sergey Fedorov writes:
>
>> On 18/04/16 20:51, Sergey Fedorov wrote:
>>> On 18/04/16 20:17, Alex Bennée wrote:
Sergey Fedorov writes:
> On 18/04/16 17:09, Alex Bennée wrote:
>> Sergey Fedorov
On 04/21/2016 08:07 AM, Sylvain Garrigues wrote:
Le 21 avr. 2016 à 15:42, Peter Maydell a écrit :
There may be something we can do here to make FreeBSD's life
easier, but we definitely can't do it on the eve of a release.
I didn’t know it was release day, my timing
The IGD OpRegion is enabled automatically when running in legacy mode,
but it can sometimes be useful in universal passthrough mode as well.
Without an OpRegion, output spigots don't work, and even though Intel
doesn't officially support physical outputs in UPT mode, it's a
useful feature. Note
Capability probing modifies wmask, which quirks may be interested in
changing themselves. Apply our BAR quirks after the capability scan
to make this possible.
Signed-off-by: Alex Williamson
---
hw/vfio/pci.c |8 +---
1 file changed, 5 insertions(+), 3
Combine VGA discovery and registration. Quirks can have dependencies
on BARs, so the quirks push out until after we've scanned the BARs.
Signed-off-by: Alex Williamson
---
hw/vfio/pci.c | 49 ++---
1 file changed, 26
This function returns success if either we setup the VGA region or
the host vfio doesn't return enough regions to support the VGA index.
This latter case doesn't make any sense. If we're asked to populate
VGA, fail if it doesn't exist and let the caller decide if that's
important.
Signed-off-by:
Enable quirks to support SandyBridge and newer IGD devices as primary
VM graphics. This requires new vfio-pci device specific regions added
in kernel v4.6 to expose the IGD OpRegion, the shadow ROM, and config
space access to the PCI host bridge and LPC/ISA bridge. VM firmware
support, SeaBIOS
Given a device specific region type and sub-type, find it. Also
cleanup return point on error in vfio_get_region_info() so that we
always return 0 with a valid pointer or -errno and NULL.
Signed-off-by: Alex Williamson
---
hw/vfio/common.c | 36
The sparse mmap capability in a vfio region info allows vfio to tell
us which sub-areas of a region may be mmap'd. Thus rather than
assuming a single mmap covers the entire region and later frobbing it
ourselves for things like the PCI MSI-X vector table, we can read that
directly from vfio.
Sergey Fedorov writes:
> On 18/04/16 20:51, Sergey Fedorov wrote:
>> On 18/04/16 20:17, Alex Bennée wrote:
>>> Sergey Fedorov writes:
On 18/04/16 17:09, Alex Bennée wrote:
> Sergey Fedorov writes:
>> diff
On 04/20/2016 04:38 PM, Lutz Vieweg wrote:
I've now a
strace -f -p 10727 -e trace=pwrite,pwritev,fdatasync,file -t 2>&1 | gzip -1 -c
>trace.gz
attached to the qemu-process.
If the incident rate stays the same, by tomorrow I should be able
to correlate newly emitted I/O-errors in the guest
This series enables "legacy mode" Intel graphics device assignment on
SandyBridge and newer CPUs when coupled with a v4.6 Linux host kernel
and updated SeaBIOS[1]. Legacy mode assignment in this context means
that we modify the VM to supply the features required for IGD, such as
an OpRegion,
On 21/04/16 16:41, Joe Clifford wrote:
On 21/04/16 15:17, Gerd Hoffmann wrote:
- When booting without the device attached, then running the device
manager to watch what happens, inserting the device results in it
appearing as normal for ~30-50 seconds before the device manager view
refreshes
On 21 April 2016 at 09:48, Aurelien Jarno wrote:
> The TCG code is quite performance sensitive, but at the same time can
> also be quite tricky. That is why asserts that can be enabled with the
> --enable-debug-tcg configure option.
>
> This used to work the following way:
>
On 04/21/2016 09:39 AM, Jason J. Herne wrote:
> The new autoconverge throttling commands have been tested for a release now.
> It
> is time to move them out of the experimental state.
>
> Signed-off-by: Jason J. Herne
> ---
> +++ b/qapi-schema.json
> @@ -480,9
On 21/04/16 15:17, Gerd Hoffmann wrote:
- When booting without the device attached, then running the device
manager to watch what happens, inserting the device results in it
appearing as normal for ~30-50 seconds before the device manager view
refreshes and the yellow warning triangle appears
On 07/04/16 18:53, Sergey Fedorov wrote:
> From: Sergey Fedorov
>
> Ensure direct jump patching in AArch64 is atomic by using
> atomic_read()/atomic_set() for code patching.
>
> Signed-off-by: Sergey Fedorov
> Signed-off-by: Sergey Fedorov
Sergey Fedorov writes:
> On 21/04/16 16:18, Alex Bennée wrote:
>> Sergey Fedorov writes:
>>> diff --git a/cpu-exec.c b/cpu-exec.c
>>> index bbfcbfb54385..065cc9159477 100644
>>> --- a/cpu-exec.c
>>> +++ b/cpu-exec.c
>>> @@ -508,11 +508,8 @@ int
The new autoconverge throttling commands have been tested for a release now. It
is time to move them out of the experimental state.
Signed-off-by: Jason J. Herne
---
hmp.c | 28 +-
migration/migration.c | 56
On 21/04/16 16:18, Alex Bennée wrote:
> Sergey Fedorov writes:
>> diff --git a/cpu-exec.c b/cpu-exec.c
>> index bbfcbfb54385..065cc9159477 100644
>> --- a/cpu-exec.c
>> +++ b/cpu-exec.c
>> @@ -508,11 +508,8 @@ int cpu_exec(CPUState *cpu)
>> next_tb
These are obviously critical to understanding interrupt delivery:
gic_enable_irq
gic_disable_irq
gic_set_irq (inbound irq from device models)
gic_update_set_irq (outbound irq to CPU)
gic_acknowledge_irq
The only one that I think might raise eyebrows is gic_update_bestirq, but I've
(sadly)
From: Sergey Fedorov
The value returned from tcg_qemu_tb_exec() is the value passed to the
corresponding tcg_gen_exit_tb() at translation time of the last TB
attempted to execute. It is a little confusing to store it in a variable
named 'next_tb'. In fact, it is a
On Tue, Apr 19, 2016 at 08:37:13AM +, Gonglei (Arei) wrote:
> 1.6.1.1 Driver Requirements: Session operation
> The driver MUST set the control type with VIRTIO_CRYPTO_CTRL_CREATE_SESSION
> before the request is preceded by an operation header when executing session
> creation:
Based on the
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
[Alex Bennée: #ifndef replay code to match elided functions]
Signed-off-by: Alex Bennée
Signed-off-by: Sergey Fedorov
---
cpu-exec.c | 8
1
From: Alex Bennée
Put some comments and improve code structure. This should help reading
the code.
Signed-off-by: Alex Bennée
[Sergey Fedorov: provide commit message; bring back resetting of
tb_invalidated_flag]
Signed-off-by: Sergey Fedorov
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
[Sergey Fedorov: eliminate the field entirely in user-mode]
Signed-off-by: Sergey Fedorov
Reviewed-by: Richard Henderson
Reviewed-by: Alex Bennée
On Thu, Apr 21, 2016 at 04:43:45PM +0300, Michael S. Tsirkin wrote:
> This adds a flag to enable/disable bypassing the IOMMU by
> virtio devices.
>
> This is on top of patch
> http://article.gmane.org/gmane.comp.emulators.qemu/403467
> virtio: convert to use DMA api
>
> Tested with patchset
>
Add a Xenstore directory for each supported pv backend. This will allow
Xen tools to decide which backend type to use in case there are
multiple possibilities.
The information is added under
/local/domain//device-model//backends
before the "running" state is written to Xenstore. Using a directory
On Thu, Apr 21, 2016 at 03:56:53PM +0100, Stefan Hajnoczi wrote:
> On Thu, Apr 21, 2016 at 04:43:45PM +0300, Michael S. Tsirkin wrote:
> > This adds a flag to enable/disable bypassing the IOMMU by
> > virtio devices.
> >
> > This is on top of patch
> >
From: Sergey Fedorov
This patch series consists of various general TCG clean-up patches extracted
from Paolo's MTTCG tree [1] and Alex's MTTCG base enablement tree [2]. I also
add here a patch from myself to rework tb_invalidated_flag based on the Paolo's
"tcg: move
From: Sergey Fedorov
'tb_invalidated_flag' was meant to catch two events:
* some TB has been invalidated by tb_phys_invalidate();
* the whole translation buffer has been flushed by tb_flush().
Then it was checked:
* in cpu_exec() to ensure that the last executed TB can
The NBD protocol does not (yet) force any alignment constraints
on clients. Even though qemu NBD clients always send requests
that are aligned to 512 bytes, we must be prepared for non-qemu
clients that don't care about alignment (even if it means they
are less efficient). Our use of blk_read()
Sergey Fedorov writes:
> From: Sergey Fedorov
>
> In user mode, there's only a static address translation, TBs are always
> invalidated properly and direct jumps are reset when mapping change.
> Thus the destination address is always valid for
On 18/04/16 20:51, Sergey Fedorov wrote:
> On 18/04/16 20:17, Alex Bennée wrote:
>> Sergey Fedorov writes:
>>> On 18/04/16 17:09, Alex Bennée wrote:
Sergey Fedorov writes:
> diff --git a/cpu-exec.c b/cpu-exec.c
>>> (snip)
> @@ -507,14
On Thu, 04/21 15:20, Michael S. Tsirkin wrote:
> On Thu, Apr 21, 2016 at 10:04:28AM +0800, Fam Zheng wrote:
> > This ensures the bdrv_drained_begin() in block layer is effective and
> > fixes launchpad bug #1570134.
> >
> > Signed-off-by: Fam Zheng
> > ---
> >
> - When booting without the device attached, then running the device
> manager to watch what happens, inserting the device results in it
> appearing as normal for ~30-50 seconds before the device manager view
> refreshes and the yellow warning triangle appears next to the IC9 UHCI
> device
Le 21 avr. 2016 à 15:42, Peter Maydell a écrit :
>
> There may be something we can do here to make FreeBSD's life
> easier, but we definitely can't do it on the eve of a release.
I didn’t know it was release day, my timing is not perfect then, sorry about
that, I
Add Stefano and Anthony
On Thu, Apr 21, 2016 at 04:43:45PM +0300, Michael S. Tsirkin wrote:
> This adds a flag to enable/disable bypassing the IOMMU by
> virtio devices.
>
> This is on top of patch
> http://article.gmane.org/gmane.comp.emulators.qemu/403467
> virtio: convert to use DMA api
>
>
On Wed, Apr 20, 2016 at 01:41:24AM +, Li, Liang Z wrote:
> > Cc: Rik van Riel; v...@zeniv.linux.org.uk; linux-ker...@vger.kernel.org;
> > quint...@redhat.com; amit.s...@redhat.com; pbonz...@redhat.com;
> > dgilb...@redhat.com; linux...@kvack.org; k...@vger.kernel.org; qemu-
> >
This adds a flag to enable/disable bypassing the IOMMU by
virtio devices.
This is on top of patch
http://article.gmane.org/gmane.comp.emulators.qemu/403467
virtio: convert to use DMA api
Tested with patchset
http://article.gmane.org/gmane.linux.kernel.virtualization/27545
virtio-pci: iommu
On 21 April 2016 at 14:15, Sylvain Garrigues
wrote:
> Le 21 avr. 2016 à 14:54, Peter Maydell a écrit :
>> On 21 April 2016 at 13:50, Sylvain Garrigues
>> wrote:
>>> BTW, would be great to be able to set the
Sergey Fedorov writes:
> From: Sergey Fedorov
>
> We don't take care of direct jumps when address mapping changes. Thus we
> must be sure to generate direct jumps so that they always keep valid
> even if address mapping changes. Luckily, we can
Le 21 avr. 2016 à 14:54, Peter Maydell a écrit :
> On 21 April 2016 at 13:50, Sylvain Garrigues
> wrote:
>> It does prevent FreeBSD to boot correctly.
>>
>> With that patch and
>> #define KERNEL_LOAD_ADDR 0x0020
>> in arm/boot/boot.c,
On 21 April 2016 at 13:50, Sylvain Garrigues
wrote:
> It does prevent FreeBSD to boot correctly.
>
> With that patch and
> #define KERNEL_LOAD_ADDR 0x0020
> in arm/boot/boot.c, official FreeBSD RPI2 images boot like a charm :-)
This is the kind of thing that is
It does prevent FreeBSD to boot correctly.
With that patch and
#define KERNEL_LOAD_ADDR 0x0020
in arm/boot/boot.c, official FreeBSD RPI2 images boot like a charm :-)
BTW, would be great to be able to set the load addr on the command line,
wouldn’t it?
> Le 21 avr. 2016 à 14:45, Peter
On 21 April 2016 at 11:41, Sylvain Garrigues
wrote:
> As the framebuffer settings are copied into the result message before
> it is reconfigured, inconsistent behavior can happen when, for instance,
> you set with a sinle message the width, height, and depth, and ask
On Thu, Apr 21, 2016 at 10:04:28AM +0800, Fam Zheng wrote:
> This ensures the bdrv_drained_begin() in block layer is effective and
> fixes launchpad bug #1570134.
>
> Signed-off-by: Fam Zheng
> ---
> hw/virtio/virtio.c | 7 ---
> 1 file changed, 4 insertions(+), 3
On 20 April 2016 at 22:35, Sylvain Garrigues
wrote:
> Signed-off-by: Sylvain Garrigues
> ---
> hw/arm/boot.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index
On Thu, 04/21 13:42, Kevin Wolf wrote:
> Am 21.04.2016 um 10:57 hat Fam Zheng geschrieben:
> > On Thu, 04/21 10:07, Kevin Wolf wrote:
> > > Am 21.04.2016 um 07:05 hat Fam Zheng geschrieben:
> > > > On Thu, 04/21 10:04, Fam Zheng wrote:
> > > > > This ensures the bdrv_drained_begin() in block layer
On 21/04/16 07:44, Gerd Hoffmann wrote:
On Mi, 2016-04-20 at 22:13 +0100, Joe Clifford wrote:
Hi folks,
I'm not a coder by any stretch of the imagination so I don't have a
patch unfortunately however, this commit:
https://github.com/qemu/qemu/commit/5f77e06baa84323e5bbc96c2c7f4fe627078b210
Am 21.04.2016 um 13:35 hat Peter Maydell geschrieben:
> On 20 April 2016 at 19:09, Max Reitz wrote:
> > On 20.04.2016 02:03, Matthew Schumacher wrote:
> >> Qemu still crashes for me, but the debug is again very different. When
> >> I attach to the qemu process from gdb, it is
Am 21.04.2016 um 10:57 hat Fam Zheng geschrieben:
> On Thu, 04/21 10:07, Kevin Wolf wrote:
> > Am 21.04.2016 um 07:05 hat Fam Zheng geschrieben:
> > > On Thu, 04/21 10:04, Fam Zheng wrote:
> > > > This ensures the bdrv_drained_begin() in block layer is effective and
> > > > fixes launchpad bug
On 20 April 2016 at 19:09, Max Reitz wrote:
> On 20.04.2016 02:03, Matthew Schumacher wrote:
>> Qemu still crashes for me, but the debug is again very different. When
>> I attach to the qemu process from gdb, it is unable to provide a
>> backtrace when it crashes. The log
Public bug reported:
As the framebuffer settings are copied into the result message before it
is reconfigured, inconsistent behavior can happen when, for instance,
you set with a single message the width, height, and depth, and ask at
the same time to allocate the buffer and get the pitch and the
* Li, Tianyou (tianyou...@intel.com) wrote:
> Hi Artyom, Dave & others,
>
> An update: I have tried to use -mem-path option to make a file-backed memory.
> I have tried to write a particular physical address in guest Linux OS with
> specific value to verify the persistency characteristics. The
Paolo Bonzini writes:
> Avoid need for qemu/log.h inclusion, and make the function static too.
>
> Signed-off-by: Paolo Bonzini
Reviewed-by: Alex Bennée
> ---
> target-arm/helper.c| 15 +++
>
Hi Artyom, Dave & others,
An update: I have tried to use -mem-path option to make a file-backed memory. I
have tried to write a particular physical address in guest Linux OS with
specific value to verify the persistency characteristics. The result is not as
we expected. Below is more details.
Paolo Bonzini writes:
> Move it to the actual users. There are some inclusions of
> qemu/host-utils.h in headers, but they are all necessary.
>
> Signed-off-by: Paolo Bonzini
This patch breaks the bisect:
make -k -j9
CCaudio/spiceaudio.o
As the framebuffer settings are copied into the result message before it is
reconfigured, inconsistent behavior can happen when, for instance, you set with
a sinle message the width, height, and depth, and ask at the same time to
allocate the buffer and get the pitch and the size.
In this
Signed-off-by: Sylvain Garrigues
---
hw/arm/boot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index 5975fbf..5876945 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -68,7 +68,7 @@ static const ARMInsnFixup
On 20 April 2016 at 16:20, Peter Maydell wrote:
> On 20 April 2016 at 15:57, Eduardo Habkost wrote:
>> On Wed, Apr 20, 2016 at 11:55:30AM -0300, Eduardo Habkost wrote:
>>> When using K: in MAINTAINERS, false positives makes
>>> get_maintainer.pl not
Paolo Bonzini writes:
> Make ARMCPU an opaque type within cpu-qom.h, and move all definitions of
> private methods, as well as all type definitions that require knowledge
> of the layout to cpu.h. This helps making files independent of NEED_CPU_H
> if they only need to
Paolo Bonzini writes:
> Make cpu-qom.h so that it is only included from cpu.h. Then there
> is no need for it to include cpu.h again.
>
> Later we will make cpu-qom.h target independent and we will _want_
> to include it from elsewhere, but for now reduce the number of
Paolo Bonzini writes:
> This decouples logging further from config-target.h
>
> Signed-off-by: Paolo Bonzini
Reviewed-by: Alex Bennée
> ---
> bsd-user/main.c| 1 +
> include/qemu/log.h | 17 ++---
>
QEMU currently crashes when using bad parameters for the
spapr-pci-host-bridge device:
$ qemu-system-ppc64 -device
spapr-pci-host-bridge,buid=0x123,liobn=0x321,mem_win_addr=0x1,io_win_addr=0x10
Segmentation fault
The problem is that spapr_tce_find_by_liobn() might return NULL, but
the code in
On Thu, 04/21 10:07, Kevin Wolf wrote:
> Am 21.04.2016 um 07:05 hat Fam Zheng geschrieben:
> > On Thu, 04/21 10:04, Fam Zheng wrote:
> > > This ensures the bdrv_drained_begin() in block layer is effective and
> > > fixes launchpad bug #1570134.
> >
> > Forgot to add to the subject, but this patch
The TCG code is quite performance sensitive, but at the same time can
also be quite tricky. That is why asserts that can be enabled with the
--enable-debug-tcg configure option.
This used to work the following way:
| #include "config.h"
|
| ...
|
| #if !defined(CONFIG_DEBUG_TCG) &&
Check for CONFIG_DEBUG_TCG instead of NDEBUG, drop now useless code.
Cc: Richard Henderson
Signed-off-by: Aurelien Jarno
---
tcg/aarch64/tcg-target.inc.c | 4 ++--
tcg/arm/tcg-target.inc.c | 2 +-
tcg/i386/tcg-target.inc.c| 2 +-
Am 20.04.2016 um 20:38 hat Rik van Riel geschrieben:
> On Wed, 2016-04-20 at 13:46 +0200, Kevin Wolf wrote:
> > Am 20.04.2016 um 12:40 hat Ric Wheeler geschrieben:
> > >
> > > On 04/20/2016 05:24 AM, Kevin Wolf wrote:
> > > >
> > > > Am 20.04.2016 um 03:56 hat Ric Wheeler geschrieben:
> > > > >
Am 21.04.2016 um 07:05 hat Fam Zheng geschrieben:
> On Thu, 04/21 10:04, Fam Zheng wrote:
> > This ensures the bdrv_drained_begin() in block layer is effective and
> > fixes launchpad bug #1570134.
>
> Forgot to add to the subject, but this patch is for 2.6.
Also CCing qemu-stable (this affects
1 - 100 of 113 matches
Mail list logo