From: Andrea Arcangeli <andrea@qumranet.com>
To: Dor Laor <dor.laor@qumranet.com>
Cc: Amit Shah <amit.shah@qumranet.com>,
Andi Kleen <andi@firstfloor.org>,
benami@il.ibm.com, Avi Kivity <avi@qumranet.com>,
Andrew Morton <akpm@linux-foundation.org>,
kvm@vger.kernel.org, aliguori@us.ibm.com, allen.m.kay@intel.com,
muli@il.ibm.com, linux-mm@kvack.org, tglx@linutronix.de,
mingo@elte.hu
Subject: Re: [PATCH] reserved-ram for pci-passthrough without VT-d capable hardware
Date: Wed, 30 Jul 2008 16:38:26 +0200 [thread overview]
Message-ID: <20080730143826.GI11494@duo.random> (raw)
In-Reply-To: <489077A6.7090105@qumranet.com>
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 usages are the ones that are totally fine with the compile
time passthrough-guest-ram decision, instead of a boot time
decision. Those host kernels will likely have RT patches (KVM works
great with preempt-RT indeed) and in turn the compile time ram
selection is the least of their problems as you can imagine ;). So you
can see my patch as an embedded-build option, similar to "Configure
standard kernel features (for small systems)" and no distro is
shipping new kernels with that feature on either.
Than if we decide 1:1 should have larger userbase instead of only the
people that knows what they're doing (i.e. 1:1 guest can destroy
linux-hypervisor) we can always add a bit of strtol parsing to 16bit
kernelloader.
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <andrea@qumranet.com>
To: Dor Laor <dor.laor@qumranet.com>
Cc: Amit Shah <amit.shah@qumranet.com>,
Andi Kleen <andi@firstfloor.org>,
benami@il.ibm.com, Avi Kivity <avi@qumranet.com>,
Andrew Morton <akpm@linux-foundation.org>,
kvm@vger.kernel.org, aliguori@us.ibm.com, allen.m.kay@intel.com,
muli@il.ibm.com, linux-mm@kvack.org, tglx@linutronix.de,
mingo@elte.hu
Subject: Re: [PATCH] reserved-ram for pci-passthrough without VT-d capable hardware
Date: Wed, 30 Jul 2008 16:38:26 +0200 [thread overview]
Message-ID: <20080730143826.GI11494@duo.random> (raw)
In-Reply-To: <489077A6.7090105@qumranet.com>
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 usages are the ones that are totally fine with the compile
time passthrough-guest-ram decision, instead of a boot time
decision. Those host kernels will likely have RT patches (KVM works
great with preempt-RT indeed) and in turn the compile time ram
selection is the least of their problems as you can imagine ;). So you
can see my patch as an embedded-build option, similar to "Configure
standard kernel features (for small systems)" and no distro is
shipping new kernels with that feature on either.
Than if we decide 1:1 should have larger userbase instead of only the
people that knows what they're doing (i.e. 1:1 guest can destroy
linux-hypervisor) we can always add a bit of strtol parsing to 16bit
kernelloader.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-30 14:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 14:52 KVM: PCIPT: direct mmio pfn check benami
2008-06-23 14:52 ` [PATCH] " benami
2008-06-25 0:57 ` Andrea Arcangeli
2008-06-25 1:18 ` [PATCH] reserved-ram for pci-passthrough without VT-d capable hardware Andrea Arcangeli
2008-06-25 1:18 ` Andrea Arcangeli, Andrea Arcangeli
2008-06-25 1:28 ` [PATCH] reserved-ram kvm-userland patch Andrea Arcangeli
2008-07-29 12:11 ` [PATCH] reserved-ram for pci-passthrough without VT-d capable hardware Andrea Arcangeli
2008-07-29 12:11 ` Andrea Arcangeli, Andrea Arcangeli
2008-07-29 12:43 ` Andi Kleen
2008-07-29 12:43 ` Andi Kleen
2008-07-29 12:53 ` Andrea Arcangeli
2008-07-29 12:53 ` Andrea Arcangeli
2008-07-29 13:17 ` Andi Kleen
2008-07-29 13:17 ` Andi Kleen
2008-07-30 6:20 ` Amit Shah
2008-07-30 6:20 ` Amit Shah
2008-07-30 12:27 ` Andi Kleen
2008-07-30 12:27 ` Andi Kleen
2008-07-30 13:58 ` Andrea Arcangeli
2008-07-30 13:58 ` Andrea Arcangeli
2008-07-30 14:16 ` Dor Laor
2008-07-30 14:16 ` Dor Laor
2008-07-30 14:38 ` Andrea Arcangeli [this message]
2008-07-30 14:38 ` Andrea Arcangeli
2008-07-30 14:22 ` FUJITA Tomonori
2008-07-30 14:22 ` FUJITA Tomonori
-- strict thread matches above, loose matches on Subject: below --
2009-04-27 17:00 Passera, Pablo R
2009-04-27 17:43 ` Andrea Arcangeli
2009-04-28 13:35 ` Passera, Pablo R
2009-04-28 18:06 ` Andrea Arcangeli
2009-05-05 19:53 ` Passera, Pablo R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080730143826.GI11494@duo.random \
--to=andrea@qumranet.com \
--cc=akpm@linux-foundation.org \
--cc=aliguori@us.ibm.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=andi@firstfloor.org \
--cc=avi@qumranet.com \
--cc=benami@il.ibm.com \
--cc=dor.laor@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=muli@il.ibm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.