public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Alok N Kataria <akataria@vmware.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	<linux-kernel@vger.kernel.org>
Subject: VMI and kmap_atomic_pte paravirt_op
Date: Thu, 25 Feb 2010 19:52:12 +0000	[thread overview]
Message-ID: <1267127532.2488.7.camel@localhost.localdomain> (raw)

Hi Alok,

How critical is the vmi_kmap_atomic_pte pv_mmu_op hook to VMI? Is it
required for correct functionality or is it simply an optimisation?

We think we may be able to do away with the Xen version of the hook and
if VMI (which is deprecated) can live without it and you agree then I'll
cook up a patch to remove it altogether.

Thanks,
Ian.



             reply	other threads:[~2010-02-25 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 19:52 Ian Campbell [this message]
2010-02-25 20:15 ` VMI and kmap_atomic_pte paravirt_op Jeremy Fitzhardinge
2010-02-25 20:32 ` Alok Kataria
2010-02-26  9:04   ` Ian Campbell

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=1267127532.2488.7.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=akataria@vmware.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox