] reserved-ram for pci-passthrough without VT-d
capable hardware
On Tue, Apr 28, 2009 at 07:35:26AM -0600, Passera, Pablo R wrote:
- Against which kernel version was this patch generated?
I don't remember exactly (I was just using an upstream hg checkout and
I didn't record its hash value) but I think
, Pablo R
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] reserved-ram for pci-passthrough without VT-d
capable hardware
Hello Pablo,
On Mon, Apr 27, 2009 at 11:00:51AM -0600, Passera, Pablo R wrote:
Andrea,
We are working with embedded hardware that does not have
VT-d and we need 1-1 mapping
On Tue, Apr 28, 2009 at 07:35:26AM -0600, Passera, Pablo R wrote:
- Against which kernel version was this patch generated?
I don't remember exactly (I was just using an upstream hg checkout and
I didn't record its hash value) but I think you can go back to when
e820.c was still shared and it'll
Andrea,
We are working with embedded hardware that does not have VT-d and we
need 1-1 mapping. I wonder which is the status of this patch. Have you
continued updating it with the latest KVM version?
Regards,
Pablo
On Wed, Jul 30, 2008 at 05:16:06PM +0300, Dor Laor wrote:
In addition
Hello Pablo,
On Mon, Apr 27, 2009 at 11:00:51AM -0600, Passera, Pablo R wrote:
Andrea,
We are working with embedded hardware that does not have
VT-d and we need 1-1 mapping. I wonder which is the status of this
patch. Have you continued updating it with the latest KVM version?
Sorry to
* On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
I'm not so interested to go there right now, because while this code
is useful right now because the majority of systems out there lacks
VT-d/iommu, I suspect this code could be nuked in the long
run when all systems will ship with that,
On Wed, Jul 30, 2008 at 11:50:43AM +0530, Amit Shah wrote:
* On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
I'm not so interested to go there right now, because while this code
is useful right now because the majority of systems out there lacks
VT-d/iommu, I suspect this code could
On Wed, Jul 30, 2008 at 11:50:43AM +0530, Amit Shah wrote:
* On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
I'm not so interested to go there right now, because while this code
is useful right now because the majority of systems out there lacks
VT-d/iommu, I suspect this code could
Andrea Arcangeli wrote:
On Wed, Jul 30, 2008 at 11:50:43AM +0530, Amit Shah wrote:
* On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
I'm not so interested to go there right now, because while this code
is useful right now because the majority of systems out there lacks
VT-d/iommu, I
On Wed, Jul 30, 2008 at 05:16:06PM +0300, Dor Laor wrote:
In addition KVM is used in embedded too and things are slower there, we
know of a specific use case (production) that demands
1:1 mapping and can't use VT-d
Since you mentioned this ;), I take opportunity to add that those
embedded
On Wed, 30 Jul 2008 15:58:46 +0200
Andrea Arcangeli [EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 11:50:43AM +0530, Amit Shah wrote:
* On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
I'm not so interested to go there right now, because while this code
is useful right now because
From: Andrea Arcangeli [EMAIL PROTECTED]
The reserved RAM can be mapped by virtualization software with
/dev/mem to create a 1:1 mapping between guest physical (bus) address
and host physical (bus) address. This will allow pci passthrough with
DMA for the guest using the ram with the 1:1 mapping.
This is a port to current linux-2.6.git of the previous reserved-ram
patch. Let me know if there's a chance to get this acked and
included. Anything that isn't at compile time would require much
I still think runtime would be far better. Nobody really wants
a proliferation of more weird
On Tue, Jul 29, 2008 at 02:43:17PM +0200, Andi Kleen wrote:
This is a port to current linux-2.6.git of the previous reserved-ram
patch. Let me know if there's a chance to get this acked and
included. Anything that isn't at compile time would require much
I still think runtime would be far
I'm not so interested to go there right now, because while this code
is useful right now because the majority of systems out there lacks
VT-d/iommu, I suspect this code could be nuked in the long
run when all systems will ship with that, which is why I kept it all
Actually at least on Intel
From: Andrea Arcangeli [EMAIL PROTECTED]
This has to be applied to the host kernel and for example specifying a
relocation address of 0x2000 it will allow to start kvm guests
capable of pci-passthrough up to -m 512 by passing the
-reserved-ram parameter in the command line. There's no risk of
16 matches
Mail list logo
