On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote:
Added the match table and pointers for ACPI probing to the driver.
This uses the same identifier for virt devices as being used for qemu
ARM64 ACPI support.
ACPI spec 5.0 allows the use of PCI vendor IDs.
Since we have one for virtio, it seems neater to use that
rather than LNRO. For the device ID, use 103F which is a legacy ID that
isn't used in virtio PCI spec - seems to make sense since virtio-mmio is
a legacy device but we don't know the correct
On 28 July 2015 at 11:33, G Gregory graeme.greg...@linaro.org wrote:
We assigned LNRO in ASWG to avoid collisions with our prototypes/real
platforms so it makes sense to me to switch to QEMU.
So just to check, if we switch virtio-mmio from an LNRO0005 ID
to a QEMU ID we aren't going to
On Wed, Jul 29, 2015 at 06:52:29PM +0100, Peter Maydell wrote:
On 28 July 2015 at 11:33, G Gregory graeme.greg...@linaro.org wrote:
We assigned LNRO in ASWG to avoid collisions with our prototypes/real
platforms so it makes sense to me to switch to QEMU.
So just to check, if we switch
2015-07-29 오후 9:46에 Daniel Vetter 이(가) 쓴 글:
On Wed, Jul 29, 2015 at 01:16:14PM +0100, Mel Gorman wrote:
On Wed, Jul 29, 2015 at 12:55:54PM +0200, Daniel Vetter wrote:
On Wed, Jul 29, 2015 at 11:49:45AM +0100, Mel Gorman wrote:
On Mon, Jul 13, 2015 at 05:35:15PM +0900, Gioh Kim wrote:
My
On 29/07/2015 02:47, Andy Lutomirski wrote:
If new kernels ignore the IOMMU for devices that don't set the flag
and there are physical devices that already exist and don't set the
flag, then those devices won't work reliably on most modern
non-virtual platforms, PPC included.
Are
On 2015-07-29 01:21, Benjamin Herrenschmidt wrote:
On Tue, 2015-07-28 at 15:43 -0700, Andy Lutomirski wrote:
New QEMU
always advertises this feature flag. If iommu=on, QEMU's virtio
devices refuse to work unless the driver acknowledges the flag.
This should be configurable.
On 2015-07-29 10:17, Paolo Bonzini wrote:
On 29/07/2015 02:47, Andy Lutomirski wrote:
If new kernels ignore the IOMMU for devices that don't set the flag
and there are physical devices that already exist and don't set the
flag, then those devices won't work reliably on most modern
On Wed, 2015-07-29 at 10:17 +0200, Paolo Bonzini wrote:
On 29/07/2015 02:47, Andy Lutomirski wrote:
If new kernels ignore the IOMMU for devices that don't set the flag
and there are physical devices that already exist and don't set the
flag, then those devices won't work reliably on
On Wed, Jul 29, 2015 at 10:01:35AM +0800, Shannon Zhao wrote:
On 2015/7/29 5:10, Peter Maydell wrote:
On 28 July 2015 at 21:28, G Gregory graeme.greg...@linaro.org wrote:
On 28 July 2015 at 21:12, Peter Maydell peter.mayd...@linaro.org wrote:
Mmm. I'm not terribly happy about stuff
On Wed, Jul 29, 2015 at 11:49:45AM +0100, Mel Gorman wrote:
On Mon, Jul 13, 2015 at 05:35:15PM +0900, Gioh Kim wrote:
My ARM-based platform occured severe fragmentation problem after long-term
(several days) test. Sometimes even order-3 page allocation failed. It has
memory size 512MB ~
On Wed, Jul 29, 2015 at 01:16:14PM +0100, Mel Gorman wrote:
On Wed, Jul 29, 2015 at 12:55:54PM +0200, Daniel Vetter wrote:
On Wed, Jul 29, 2015 at 11:49:45AM +0100, Mel Gorman wrote:
On Mon, Jul 13, 2015 at 05:35:15PM +0900, Gioh Kim wrote:
My ARM-based platform occured severe
12 matches
Mail list logo
