From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Linux Kernel Summit 2012 hallway talks - PV MMU, PVH, hpa, tglrx, stefano and me.
Date: Mon, 10 Dec 2012 10:08:49 -0500 [thread overview]
Message-ID: <20121210150849.GC6955@localhost.localdomain> (raw)
In-Reply-To: <1355131949.31710.95.camel@zakaz.uk.xensource.com>
On Mon, Dec 10, 2012 at 09:32:29AM +0000, Ian Campbell wrote:
> On Fri, 2012-12-07 at 17:05 +0000, Konrad Rzeszutek Wilk wrote:
>
> > Anyhow, once the PVH works - so can do SMP guests, does
> > properly interrupt delivery, etc, we would obsolete the PV MMU
> > mode in 5 years. This means that arch/x86/xen/p2m.c and arch/x86/xen/mmu.c
> > along with a host of paravirt interfaces would be #ifdef-ed out.
> > There would also be a note in the Documentation/deprecate-schedule
> > pointing that out. If everything time-wise aligns itself that
> > means 2013 is when PVH has it debut and will have its kinks worked
> > out. 2018 is when PV MMU would be obsoleted. The impact is that in
> > 2018 users would need Intel VT-d or AMD VI-IOMMU capable machine to run
> > the latest Linux dom0 kernel with device drivers on x86.
> > You would still be able to run the ancient PV kernels (like 2.6.18) as
> > guests - just not as a dom0.
>
> I'm not sure I follow -- why does this future change in mainline Linux
> have any impact on other kernel trees and their ability to run as dom0?
It does not. Thank you for catching that.
The last sentence should not have 'just not as dom0'.
>
> Ian.
>
prev parent reply other threads:[~2012-12-10 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 17:05 Linux Kernel Summit 2012 hallway talks - PV MMU, PVH, hpa, tglrx, stefano and me Konrad Rzeszutek Wilk
2012-12-10 9:32 ` Ian Campbell
2012-12-10 15:08 ` Konrad Rzeszutek Wilk [this message]
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=20121210150849.GC6955@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).