On Wed, 15 Jul 2015 19:24:33 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Jul 15, 2015 at 06:01:42PM +0200, Igor Mammedov wrote:
> > On Wed, 15 Jul 2015 17:08:27 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > > > Hi,
> > > >
On 07/16/2015 02:42 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2015 at 03:56:07PM +0800, Jason Wang wrote:
>> Commit 032a74a1c0fcdd5fd1c69e56126b4c857ee36611
>> ("virtio-net: byteswap virtio-net header") breaks any layout by
>> requiring out_sg[0].iov_len >= n->guest_hdr_len. Fixing this by
On Wed, Jul 15, 2015 at 03:56:07PM +0800, Jason Wang wrote:
> Commit 032a74a1c0fcdd5fd1c69e56126b4c857ee36611
> ("virtio-net: byteswap virtio-net header") breaks any layout by
> requiring out_sg[0].iov_len >= n->guest_hdr_len. Fixing this by
> copying header to temporary buffer if swap is needed, a
- Original Message -
> From: "Amit Shah"
> To: "Pankaj Gupta"
> Cc: qemu-devel@nongnu.org, m...@redhat.com
> Sent: Thursday, 16 July, 2015 11:35:36 AM
> Subject: Re: [Qemu-devel] [PATCH 2/2 v3] virtio-rng: Serve pending request if
> any after timer bumps up quota.
>
> On (Wed) 15 Jul
On (Wed) 15 Jul 2015 [23:44:52], Nils Carlson wrote:
> On Mon, 13 Jul 2015, Nils Carlson wrote:
>
> >On Mon, 13 Jul 2015, Amit Shah wrote:
>
>
>
> >>Also, returning TRUE there isn't right - if the connection ends, we
> >>should return FALSE.
> >
> >I agree that this seems reasonable. I will cha
On Thu, Jul 16, 2015 at 01:54:38PM +0800, Jason Wang wrote:
>
>
> On 07/15/2015 07:23 PM, Michael S. Tsirkin wrote:
> > On Wed, Jul 15, 2015 at 03:56:07PM +0800, Jason Wang wrote:
> >> Commit 032a74a1c0fcdd5fd1c69e56126b4c857ee36611
> >> ("virtio-net: byteswap virtio-net header") breaks any layou
On (Wed) 15 Jul 2015 [17:46:48], Pankaj Gupta wrote:
> We are arming timer when we get first request from guest.
> Even if guest pulls all the data we will be serving guest
> only when timer bumps up new quota. When timer expires
> we check if we have a pending request from guest, we
> serve it and
I made some time for limited testing.
The released V2.1 puts the vfio-ed RTL8168 into a zombie state when running an
IPFire VM, which requires a subsequent POWER cycle in order to let mii-tools
show anything else than 'no link' (i.e. to get the LED back on). Pushing the
reset button on the x64 m
On 07/15/2015 07:23 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2015 at 03:56:07PM +0800, Jason Wang wrote:
>> Commit 032a74a1c0fcdd5fd1c69e56126b4c857ee36611
>> ("virtio-net: byteswap virtio-net header") breaks any layout by
>> requiring out_sg[0].iov_len >= n->guest_hdr_len. Fixing this by
On 07/15/2015 06:19 PM, Fam Zheng wrote:
> v2: Don't use BH in patches 6 and 12. [Jason]
> Add Stefan's reviewed-by in all others.
> Drop trace point in patch 8 and move function body upward. [Michael]
>
> Since a90a742 "tap: Drop tap_can_send", all nics that returns false from
> .can_rec
On 07/16/2015 11:32 AM, Fam Zheng wrote:
> On Thu, 07/16 10:58, Jason Wang wrote:
>>
>> On 07/15/2015 06:19 PM, Fam Zheng wrote:
>>> eth_can_rx checks s->rxsize and returns false if it is non-zero. Because
>>> of the .can_receive semantics change, this will make the incoming queue
>>> disabled by
On Wed, 07/15 19:13, Paolo Bonzini wrote:
> This patch rewrites the ctx->dispatching optimization
I lost track, but what was the justification of this optimization?
Anyway, awesome debugging and explanations!
Fam
On Tue, Jul 14, 2015 at 10:21:54PM +1000, Alexey Kardashevskiy wrote:
> This makes use of the new "memory registering" feature. The idea is
> to provide the userspace ability to notify the host kernel about pages
> which are going to be used for DMA. Having this information, the host
> kernel can p
Hi,
When I use -machine pc,mem-merge=off|on -m 1G,slots=4,maxmem=2G, adding
memory-backend-ram object fails like below. Same failure is seen with
-machine pseries,mem-merge=on|off.
(qemu) object_add memory-backend-ram,id=ram0,size=1G
qemu-system-x86_64: util/qemu-option.c:388: qemu_opt_get_bool_
There's quite a bit of cleanup that can be done to the RTL8168 quirk,
as well as the tracing to prevent a spew of uninteresting accesses
for anything else the driver might choose to use the window registers
for besides the MSI-X table. There should be no functional change,
but it's now possible to
A small patch for stable plus a bigger patch to make tracing of this
quirk useful and restructure and comment the read/write accessors.
Thanks,
Alex
---
Alex Williamson (2):
vfio/pci: Fix RTL8168 NIC quirks
vfio/pci: Cleanup RTL8168 quirk and tracing
hw/vfio/pci.c | 90 +
The RTL8168 quirk correctly describes using bit 31 as a signal to
mark a latch/completion, but the code mistakenly uses bit 28. This
causes the Realtek driver to spin on this register for quite a while,
20k cycles on Windows 7 v7.092 driver. Then it gets frustrated and
tries to set the bit itself
On Thu, 2015-07-16 at 12:00 +0800, Chen Hanxiao wrote:
> From: Chen Fan
>
> For now, when qemu receives an error from host aer report
> by vfio pci passthough devices, qemu just terminate the guest.
> Usually user want to know what error occurred
> rather than stop the guest.
>
> This patches ad
From: Chen Fan
add 'aer' property to let user able to decide whether expose
the aer capability. by default we should disable aer feature,
because it needs configuration restrictions.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 2 ++
1 file changed, 2 insertions(+)
From: Chen Fan
Particularly, For vfio devices, Once need to recovery devices
by bus reset such as AER, we always need to reset the host bus
to recovery the devices under the bus, so we need to add pci bus
callbacks to specify to do host bus reset.
Signed-off-by: Chen Fan
Signed-off-by: Chen Han
From: Chen Fan
the function is used to get affected devices by bus reset.
so here extract it, and can used for aer soon.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 65 ++-
1 file changed, 47 insertions(+), 18
From: Chen Fan
Calling pcie_aer_init to initilize aer related registers for
vfio device, then reload physical related registers to expose
device capability.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 89 +--
From: Chen Fan
when init vfio devices done, we should test all the devices supported
aer whether conflict with others. For each one, get the hot reset
info for the affected device list. For each affected device, all
should attach to the VM and on the same slot. also, we should test
all of the no
From: Chen Fan
when the vfio device encounters an uncorrectable error in host,
the vfio_pci driver will signal the eventfd registered by this
vfio device, the results in the qemu eventfd handler getting
invoked.
this patch is to pass the error to guest and have the guest driver
recover from the
From: Chen Fan
when do virtual secondary bus reset, the vfio device under
this bus need to do host bus reset to reset the device.
so add this case.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 31 +++
1 file changed, 31 insertions(+)
dif
From: Chen Fan
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 83 +++
1 file changed, 83 insertions(+)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index ed4d87e..bab72a4 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pc
From: Chen Fan
pcie_aer_init was used to emulate an aer capability for pcie device,
but for vfio device, the aer config space size is mutable and is not
always equal to PCI_ERR_SIZEOF(0x48). it depends on where the TLP Prefix
register required, so here we add a size argument.
Signed-off-by: Chen
From: Chen Fan
the vfio_pci_hot_reset differentiate the single and multi in-used
devices for reset. but in multi case, when some dependent devices
are not assigned to VM, the devices can not be recovered by driver.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 13 +++
From: Chen Fan
For vfio device, we need to propagate the aer error to
Guest OS. we use the pcie_aer_msg() to send aer error
to guest.
Signed-off-by: Chen Fan
Reviewed-by: Marcel Apfelbaum
Signed-off-by: Chen Hanxiao
---
hw/pci/pcie_aer.c | 2 +-
include/hw/pci/pcie_aer.h | 1 +
2 fil
From: Chen Fan
Device's Offset and size can reach PCIE_CONFIG_SPACE_SIZE,
fix the corresponding assert.
Signed-off-by: Chen Fan
Reviewed-by: Marcel Apfelbaum
Signed-off-by: Chen Hanxiao
---
hw/pci/pcie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/pci/pcie.c b/hw
From: Chen Fan
For vfio pcie device, we could expose the extended capability on
PCIE bus. in order to avoid config space broken, we introduce
a copy config for parsing extended caps. and rebuild the pcie
extended config space.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pc
From: Chen Fan
this function search the capability from the end, the last
size should 0x100 - pos, not 0xff - pos.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index f9
From: Chen Fan
squeeze out vfio_pci_do_hot_reset to do host bus reset when AER recovery.
Signed-off-by: Chen Fan
Signed-off-by: Chen Hanxiao
---
hw/vfio/pci.c | 75 +++
1 file changed, 44 insertions(+), 31 deletions(-)
diff --git a/hw/v
From: Chen Fan
For now, when qemu receives an error from host aer report
by vfio pci passthough devices, qemu just terminate the guest.
Usually user want to know what error occurred
rather than stop the guest.
This patches add aer capability support for vfio device,
then pass the error to guest,
On Thu, 07/16 10:58, Jason Wang wrote:
>
>
> On 07/15/2015 06:19 PM, Fam Zheng wrote:
> > eth_can_rx checks s->rxsize and returns false if it is non-zero. Because
> > of the .can_receive semantics change, this will make the incoming queue
> > disabled by peer, until it is explicitly flushed. So w
On 07/16/2015 12:51 PM, Alex Williamson wrote:
On Thu, 2015-07-16 at 11:26 +1000, Alexey Kardashevskiy wrote:
On 07/16/2015 04:26 AM, Alex Williamson wrote:
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
The existing memory listener is called on RAM or PCI address space
which i
On 07/15/2015 06:19 PM, Fam Zheng wrote:
> eth_can_rx checks s->rxsize and returns false if it is non-zero. Because
> of the .can_receive semantics change, this will make the incoming queue
> disabled by peer, until it is explicitly flushed. So we should flush it
> when s->rxsize is becoming zero
On Thu, 2015-07-16 at 11:26 +1000, Alexey Kardashevskiy wrote:
> On 07/16/2015 04:26 AM, Alex Williamson wrote:
> > On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
> >> The existing memory listener is called on RAM or PCI address space
> >> which implies potentially different page si
On 07/15/2015 05:20 PM, Wen Congyang wrote:
> commit da51a335 adds all queues in .realize(). But if the
> guest doesn't support multiqueue, we forget to remove them. And
> we cannot handle the ctrl vq corretly. The guest will hang.
>
> Signed-off-by: Wen Congyang
> ---
Acked-by: Jason Wang
>
ping...
On 07/03/2015 05:38 PM, Zhu Guihua wrote:
ICC Bus was used for providing a hotpluggable bus for APIC and CPU,
but now we use HotplugHandler to make hotplug. So ICC Bus is
unnecessary.
This code has passed the new pc-cpu-test.
And I have tested with kvm along with kernel_irqchip=on/off,
On 07/16/2015 04:26 AM, Alex Williamson wrote:
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
The existing memory listener is called on RAM or PCI address space
which implies potentially different page size. Instead of guessing
what page size should be used, this replaces a singl
On Wed, Jul 15, 2015 at 07:24:33PM +0300, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2015 at 06:01:42PM +0200, Igor Mammedov wrote:
> > On Wed, 15 Jul 2015 17:08:27 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > > > Hi,
> > >
On 07/16/2015 04:26 AM, Alex Williamson wrote:
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
Every IOMMU has some granularity which MemoryRegionIOMMUOps::translate
uses when translating, however this information is not available outside
the translate context for various checks.
On Tue, Jul 14, 2015 at 10:43:46AM +0100, Richard W.M. Jones wrote:
> On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > 3. I'm currently only handling x86 and I/O ports. I could drop the
> >fw_cfg_dmi_whitelist and just check the signature, using mmio where
> >appropriat
From: Nils Carlson
Commit 812c1057 introduced HUP detection on unix and tcp sockets prior
to a read in tcp_chr_read. This unfortunately broke CloudStack 4.2
which relied on the old behaviour where data on a socket was readable
even if a HUP was present.
On Linux a working solution seems to be to
On 15/07/2015 22:14, Kevin Wolf wrote:
> > index 233d8f5..ae7c6cf 100644
> > --- a/aio-win32.c
> > +++ b/aio-win32.c
> > @@ -318,11 +313,11 @@ bool aio_poll(AioContext *ctx, bool blocking)
> > first = true;
> >
> > /* wait until next event */
> > -while (count > 0) {
> > +do {
On 07/14/15 22:23, Wei Huang wrote:
> SMBIOS tables present userful system hardware info to management
> applications, such as DMI tools. Even though SMBIOS was originally
> developed for Intel x86, it has been extended to both Itanium and
> ARM (32bit & 64bit). More and more ARM server releases,
On Wed, 2015-07-15 at 14:56 -0700, Gabriel Laupre wrote:
> Fix pba_offset initialization value for Chelsio T5 Virtual Function
> device. The T5 hardware has a bug in it where it reports a Pending Interrupt
> Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
> of the 0x1000 that th
Fix pba_offset initialization value for Chelsio T5 Virtual Function
device. The T5 hardware has a bug in it where it reports a Pending Interrupt
Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
of the 0x1000 that the hardware actually uses internally. As the hardware
doesn't retu
On Mon, 13 Jul 2015, Nils Carlson wrote:
On Mon, 13 Jul 2015, Amit Shah wrote:
Also, returning TRUE there isn't right - if the connection ends, we
should return FALSE.
I agree that this seems reasonable. I will change it and re-test.
I had a closer look, and it seems always returning t
On Wed, Jul 15, 2015 at 4:28 PM, Peter Maydell
wrote:
> Googling suggests "qsim" is "a project which aims, as part of the
> Manifold simulation effort at Georgia Tech, to create a thread safe
> multicore emulation library based on the QEMU emulator".
>
> My immediate guess is that this is buggy a
On 15 July 2015 at 21:02, Eduardo Habkost wrote:
> The following changes since commit 7692401a0826803522cfde533bdcc149932ddc6a:
>
> Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20150715' into staging (2015-07-15
> 17:28:59 +0100)
>
On 2014-04-24 13:01, Richard Henderson wrote:
>
> Our 32-bit build for sparc has been requiring a 64-bit capable chip
> for about 2 years now, by way of requiring move-conditional and LE
> memory instructions. But we've mostly been generating 32-bit code
> otherwise.
>
> This patch set changes t
On 15 July 2015 at 20:17, Pranith Kumar wrote:
> Hi,
>
> I occasionally get the following crash while running an AArch64 softmmu on
> an x86-64 system. I am using version 2.2 and cannot update to the latest
> version. Did anyone else see this happening? If this is fixed, I would love
> to get the
From: Radim Krčmář
W10 insider has a bug where it ignores CPUID level and interprets
CPUID.(EAX=07H, ECX=0H) incorrectly, because CPUID in fact returned
CPUID.(EAX=04H, ECX=0H); this resulted in execution of unsupported
instructions.
While it's a Windows bug, there is no reason to emulate incor
The following changes since commit 7692401a0826803522cfde533bdcc149932ddc6a:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20150715'
into staging (2015-07-15 17:28:59 +0100)
are available in the git repository at:
git://github.com/ehabkost/qemu.git tag
Now object_property_add_alias() calls g_strdup() on the target property
name, so we don't need to call g_strdup() ourselves.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index f9b178
Am 15.07.2015 um 22:15 schrieb Andrey Korolyov:
On Wed, Jul 15, 2015 at 11:07 PM, Stefan Priebe wrote:
Am 15.07.2015 um 13:32 schrieb Andrey Korolyov:
On Wed, Jul 15, 2015 at 2:20 PM, Stefan Priebe - Profihost AG
wrote:
Hi,
is there a way to query the current cpu model / type of a runni
On Wed, Jul 15, 2015 at 11:07 PM, Stefan Priebe wrote:
> Am 15.07.2015 um 13:32 schrieb Andrey Korolyov:
>>
>> On Wed, Jul 15, 2015 at 2:20 PM, Stefan Priebe - Profihost AG
>> wrote:
>>>
>>> Hi,
>>>
>>> is there a way to query the current cpu model / type of a running qemu
>>> machine?
>>>
>>> I
Am 15.07.2015 um 19:13 hat Paolo Bonzini geschrieben:
> This patch rewrites the ctx->dispatching optimization, which was the cause
> of some mysterious hangs that could be reproduced on aarch64 KVM only.
> The hangs were indirectly caused by aio_poll() and in particular by
> flash memory updates's
On Thu, Jul 09, 2015 at 09:07:39PM +0200, Radim Krčmář wrote:
> W10 insider has a bug where it ignores CPUID level and interprets
> CPUID.(EAX=07H, ECX=0H) incorrectly, because CPUID in fact returned
> CPUID.(EAX=04H, ECX=0H); this resulted in execution of unsupported
> instructions.
>
> While it
Am 15.07.2015 um 13:32 schrieb Andrey Korolyov:
On Wed, Jul 15, 2015 at 2:20 PM, Stefan Priebe - Profihost AG
wrote:
Hi,
is there a way to query the current cpu model / type of a running qemu
machine?
I mean host, kvm64, qemu64, ...
Stefan
I believe that the most proper one would be
'quer
On Sun, May 10, 2015 at 06:52:28PM +, Doran, Mark wrote:
> Hi Michael:
>
> Fortunately the ID element of ACPI in and of itself can be discussed in
> public forum venues so no problem to copy the mailing list (added to cc for
> this reply).
>
> I don't know that naming a project that is not a
The following changes since commit 7692401a0826803522cfde533bdcc149932ddc6a:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20150715'
into staging (2015-07-15 17:28:59 +0100)
are available in the git repository at:
git://github.com/ehabkost/qemu.git tags
From: Bharata B Rao
Fix a memory leak in numa_set_mem_node_id().
Signed-off-by: Bharata B Rao
Reported-by: Paolo Bonzini
Reviewed-by: Eduardo Habkost
Signed-off-by: Eduardo Habkost
---
numa.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/numa.c b/numa.c
index 3c80059
On Tue, Jun 23, 2015 at 04:07:29PM +0200, Michael S. Tsirkin wrote:
> Hello!
> QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
> it generates. This is a bit of a spec violation:
> all IDs must be registered with the ASWG.
>
> From the ASWG point of view, things are easier if a legal
Hi,
I occasionally get the following crash while running an AArch64 softmmu on
an x86-64 system. I am using version 2.2 and cannot update to the latest
version. Did anyone else see this happening? If this is fixed, I would love
to get the patch backported.
Thanks!
Program received signal SIGSEGV
On Wed, Jul 01, 2015 at 12:05:45PM -0700, Gabriel Laupre wrote:
> Fix pba_offset initialization value for Chelsio T5 Virtual Function
> device. The T5 hardware has a bug in it where it reports a Pending Interrupt
> Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
> of the 0x1000
Currently, scsi_get_configuration always returns a current
profile (DVD or CD), even when there is actually no media present.
By comparison, ide/atapi uses a default profile of 0 (MMC_PROFILE_NONE)
for this case and checks for tray_open, so let's do the same for scsi.
This fixes a problem I'm seei
On Wed, Jul 15, 2015 at 05:38:53PM +0200, Cornelia Huck wrote:
> On Wed, 15 Jul 2015 17:39:18 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Jul 15, 2015 at 04:30:51PM +0200, Cornelia Huck wrote:
> > > On Wed, 15 Jul 2015 17:11:57 +0300
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > > > > >
equest' into staging (2015-07-15
> 14:23:58 +0100)
>
> are available in the git repository at:
>
>
> git://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-target-arm-20150715
>
> for you to fetch changes up to 76e2aef392629f2b2a468f5158d5c397cc5beed2:
>
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
> Every IOMMU has some granularity which MemoryRegionIOMMUOps::translate
> uses when translating, however this information is not available outside
> the translate context for various checks.
>
> This adds a get_page_sizes callback to
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
> The existing memory listener is called on RAM or PCI address space
> which implies potentially different page size. Instead of guessing
> what page size should be used, this replaces a single IOMMU memory
> listener by two, one per su
On Tue, 2015-07-14 at 22:21 +1000, Alexey Kardashevskiy wrote:
> So far we were managing not to have an IOMMU type stored anywhere but
> since we are going to implement different behavior for different IOMMU
> types in the same memory listener, we need to know IOMMU type after
> initialization.
>
comments below
On 07/15/15 19:13, Paolo Bonzini wrote:
> This patch rewrites the ctx->dispatching optimization, which was the cause
> of some mysterious hangs that could be reproduced on aarch64 KVM only.
> The hangs were indirectly caused by aio_poll() and in particular by
> flash memory updates'
On Wed, Jul 15, 2015 at 06:28:54PM +0100, Varun Sethi wrote:
> > > > On Fri, Jun 12, 2015 at 03:20:04PM +0100, Baptiste Reynal wrote:
> > > > > The ARM SMMU has support for 2-stages address translations,
> > > > > allowing a virtual address to be translated at two levels:
> > > > > - Stage 1 transl
Hi Will,
> -Original Message-
> From: Will Deacon [mailto:will.dea...@arm.com]
> Sent: Tuesday, July 14, 2015 4:34 PM
> To: Sethi Varun-B16395
> Cc: Baptiste Reynal; io...@lists.linux-foundation.org;
> t...@virtualopensystems.com; qemu-devel@nongnu.org
> Subject: Re: [RFC 0/6] vSMMU initia
On Wed, Jul 15, 2015 at 06:01:42PM +0200, Igor Mammedov wrote:
> On Wed, 15 Jul 2015 17:08:27 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > > Hi,
> > >
> > > A while ago I was pondering on the options available for retrieving
> >
This patch rewrites the ctx->dispatching optimization, which was the cause
of some mysterious hangs that could be reproduced on aarch64 KVM only.
The hangs were indirectly caused by aio_poll() and in particular by
flash memory updates's call to blk_write(), which invokes aio_poll().
Fun stuff: they
** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Trusty)
Importanc
On 07/15/2015 09:42 AM, Max Reitz wrote:
> Hi,
>
> Indeed using non-raw images should not be used over NBD. The warning
> however is not superfluous, since qemu does indeed probe the image
> format, so a malicious guest might write a qcow2 header into the raw
> image, thus making qemu probe a qcow
On Wed, Jul 15, 2015 at 7:08 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2015 at 06:26:03PM +0300, Andrey Korolyov wrote:
>> On Wed, Jul 15, 2015 at 6:18 PM, Igor Mammedov wrote:
>> > On Thu, 9 Jul 2015 20:04:35 +0300
>> > Andrey Korolyov wrote:
>> >
>> >> On Wed, Jul 8, 2015 at 6:46 PM, Igo
** Tags added: upstream
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
Status in QEMU:
New
Status in qemu package in Ubuntu:
On 13 July 2015 at 17:50, Alexander Graf wrote:
> The Linux kernel on aarch64 creates a page table entry at early bootup
> that spans the 2MB range on memory spanning the fdt start address:
>
> [ ALIGN_DOWN(fdt, 2MB) ... ALIGN_DOWN(fdt, 2MB) + 2MB ]
>
> This means that when our current 4k alignm
Hi Baptiste,
> -Original Message-
> From: Baptiste Reynal [mailto:b.rey...@virtualopensystems.com]
> Sent: Wednesday, July 15, 2015 7:08 PM
> To: Will Deacon
> Cc: Sethi Varun-B16395; io...@lists.linux-foundation.org;
> t...@virtualopensystems.com; qemu-devel@nongnu.org
> Subject: Re: [RFC
ping
> -Original Message-
> From: Stalley, Sean
> Sent: Wednesday, July 01, 2015 11:20 AM
> To: qemu-devel@nongnu.org
> Cc: m...@redhat.com; Stalley, Sean
> Subject: [PATCH v2 0/1] Add support for PCI Enhanced Allocation "BARs"
>
> Changes from v1:
> - added a cover letter with a ch
On Wed, Jul 15, 2015 at 06:26:03PM +0300, Andrey Korolyov wrote:
> On Wed, Jul 15, 2015 at 6:18 PM, Igor Mammedov wrote:
> > On Thu, 9 Jul 2015 20:04:35 +0300
> > Andrey Korolyov wrote:
> >
> >> On Wed, Jul 8, 2015 at 6:46 PM, Igor Mammedov wrote:
> >> > On Wed, 8 Jul 2015 13:01:05 +0300
> >> >
On Wed, Jul 15, 2015 at 05:12:01PM +0200, Igor Mammedov wrote:
> On Thu, 9 Jul 2015 13:47:17 +0200
> Igor Mammedov wrote:
>
> there also is yet another issue with vhost-user. It also has
> very low limit on amount of memory regions (if I recall correctly 8)
> and it's possible to trigger even wi
On 14/07/2015 16:45, Aurelien Jarno wrote:
> When a LWL, LWR, LDL or LDR instruction triggers a page fault, QEMU
> currently reports the aligned address in CP0 BadVAddr, while the Windows
> NT kernel expects the unaligned address.
>
> This patch adds a byte access with the unaligned address at the
From: Alexander Graf
The Linux kernel on aarch64 creates a page table entry at early bootup
that spans the 2MB range on memory spanning the fdt start address:
[ ALIGN_DOWN(fdt, 2MB) ... ALIGN_DOWN(fdt, 2MB) + 2MB ]
This means that when our current 4k alignment happens to fall at the end
of th
The SCTLR_EL3 cpreg definition was implicitly resetting the
register state to 0, which is both wrong and clashes with
the reset done via the SCTLR definition (since sctlr[3]
is unioned with sctlr_s). This went unnoticed until recently,
when an unrelated change (commit a903c449b41f105aa) happened to
in the git repository at:
git://git.linaro.org/people/pmaydell/qemu-arm.git
tags/pull-target-arm-20150715
for you to fetch changes up to 76e2aef392629f2b2a468f5158d5c397cc5beed2:
hw/arm/boot: Increase fdt alignment (2015-07-15 17:1
On Wed, 15 Jul 2015 17:08:27 +0300
"Michael S. Tsirkin" wrote:
> On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > Hi,
> >
> > A while ago I was pondering on the options available for retrieving
> > a fw_cfg blob from the guest-side (now that we can insert fw_cfg
> > files on
On 2015-07-15 17:27, Paolo Bonzini wrote:
> The new argument lets you pick uxtw or uxtx mode for the offset
> register. For now, all callers pass TCG_TYPE_I64 so that uxtx
> is generated. The bits for uxtx are removed from I3312_TO_I3310.
>
> Reported-by: Leon Alrae
> Signed-off-by: Paolo Bonzi
On 2015-07-15 17:27, Paolo Bonzini wrote:
> Thanks to the previous patch, it is now easy for tcg_out_qemu_ld and
> tcg_out_qemu_st to use a 32-bit zero extended offset. However, the
> guest base register x28 must be the base and addr_reg must be the
> index.
>
> Reported-by: Leon Alrae
> Signed-
On 30/06/2015 14:18, Leon Alrae wrote:
> On 29/06/2015 11:20, Andrew Bennett wrote:
>> From: Andrew Bennett
>>
>> For the MIPS N64 ABI when QEMU reads the break/trap instruction so that
>> it can inspect the break/trap code it reads 8 rather than 4 bytes
>> which means it finds the code field from
Hi,
Indeed using non-raw images should not be used over NBD. The warning
however is not superfluous, since qemu does indeed probe the image
format, so a malicious guest might write a qcow2 header into the raw
image, thus making qemu probe a qcow2 image the next time the same
configuration is used.
On Wed, 15 Jul 2015 17:39:18 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Jul 15, 2015 at 04:30:51PM +0200, Cornelia Huck wrote:
> > On Wed, 15 Jul 2015 17:11:57 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > > > > > Fine, but revision is negotiated way before features are
> > > > > > > probed
Hello!
> Here GICV3_INTERNAL is used, but kvm_arch_gicv3_set_irq relies on
> kvm_arm_gic_set_irq which is using GIC_INTERNAL, so the GICv3 related
> code is using both defines.
The change relies on these definitions being equal. Ok, i agree this is a kind
of hack and will
redo this in v5.
> A
On Thu, 9 Jul 2015 20:04:35 +0300
Andrey Korolyov wrote:
> On Wed, Jul 8, 2015 at 6:46 PM, Igor Mammedov wrote:
> > On Wed, 8 Jul 2015 13:01:05 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > [...]
> >> - this fixes qemu on current kernels, so it's a bugfix
> >>
> >> - this changes the semantics
1 - 100 of 293 matches
Mail list logo
