public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Mukesh Rathor <mukesh.rathor@oracle.com>,
	Mike Rapoport <mike.rapoport@gmail.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	xen-devel@lists.xensource.com
Subject: Re: [QUERY] lguest64
Date: Mon, 5 Aug 2013 12:50:40 -0400	[thread overview]
Message-ID: <20130805165040.GC22093@phenom.dumpdata.com> (raw)
In-Reply-To: <20130804123708.GM6042@redhat.com>

On Sun, Aug 04, 2013 at 03:37:08PM +0300, Gleb Natapov wrote:
> On Fri, Aug 02, 2013 at 03:09:34PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jul 31, 2013 at 06:25:04AM -0700, H. Peter Anvin wrote:
> > > On 07/31/2013 06:17 AM, Konrad Rzeszutek Wilk wrote:
> > > >>
> > > >> The big problem with pvops is that they are a permanent tax on future
> > > >> development -- a classic case of "the hooks problem."  As such it is
> > > >> important that there be a real, significant, use case with enough users
> > > >> to make the pain worthwhile.  With Xen looking at sunsetting PV support
> > > >> with a long horizon, it might currently be possible to remove pvops some
> > > > 
> > > > PV MMU parts specifically.
> > > > 
> > > 
> > > Pretty much stuff that is driverized on plain hardware doesn't matter.
> > > What are you looking at with respect to the basic CPU control state?
> > 
> > 
> > CC-ing Mukesh here.
> > 
> > Let me iterate down what the experimental patch uses:
> > 
> >          struct pv_init_ops pv_init_ops;                                         
> > 		[still use xen_patch, but I think that is not needed anymore]
> > 
> >          struct pv_time_ops pv_time_ops;                                         
> > 		[we need that as we are using the PV clock source]
> > 
> >          struct pv_cpu_ops pv_cpu_ops;                                           
> > 		[only end up using cpuid. This one is a tricky one. We could
> > 		 arguable remove it but it does do some filtering - for example
> > 	 	 THERM is turned off, or MWAIT if a certain hypercall tells us to
> > 		 disable that. Since this is now a trapped operation this could be
> > 		 handled in the hypervisor - but then it would be in charge of
> > 		 filtering certain CPUID - and this is at bootup - so there is not
> > 		 user interaction. This needs a bit more of thinking]
> > 
> read_msr/write_msr in this one make all msr accesses safe. IIRC there
> are MSRs that Linux uses without checking cpuid bits.
> IA32_PERF_CAPABILITIES for instance is used without checking PDCM bit.

Right, those are needed as well. Completly forgot about them.
> 
> 
> --
> 			Gleb.

  reply	other threads:[~2013-08-05 16:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  9:06 [QUERY] lguest64 Ramkumar Ramachandra
2013-07-19 17:29 ` H. Peter Anvin
2013-07-19 17:42   ` Ramkumar Ramachandra
2013-07-19 18:46     ` H. Peter Anvin
2013-07-19 20:36       ` richard -rw- weinberger
2013-08-01 17:22       ` Ramkumar Ramachandra
2013-08-01 13:04         ` Alex Elsayed
2013-07-23  1:28   ` Rusty Russell
2013-07-31  9:39     ` Mike Rapoport
2013-07-31 12:17       ` H. Peter Anvin
2013-07-31 13:07         ` Mike Rapoport
2013-07-31 13:19           ` H. Peter Anvin
2013-07-31 14:32             ` Mike Rapoport
2013-08-01  2:12           ` Rusty Russell
2013-08-02 14:27             ` H. Peter Anvin
2013-07-31 13:17         ` Konrad Rzeszutek Wilk
2013-07-31 13:25           ` H. Peter Anvin
2013-08-02 19:09             ` Konrad Rzeszutek Wilk
2013-08-04 12:37               ` Gleb Natapov
2013-08-05 16:50                 ` Konrad Rzeszutek Wilk [this message]
2013-08-05 16:59                   ` H. Peter Anvin
2013-08-05 17:16                     ` Konrad Rzeszutek Wilk
2013-07-31 15:31       ` Borislav Petkov
2013-08-01  7:18         ` Mike Rapoport
2013-08-08 19:15       ` Richard W.M. Jones

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=20130805165040.GC22093@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=artagnon@gmail.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.rapoport@gmail.com \
    --cc=mukesh.rathor@oracle.com \
    --cc=rusty@rustcorp.com.au \
    --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