From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH V3 3/6]: PVH: mmu related changes.
Date: Thu, 18 Oct 2012 11:47:10 +0100 [thread overview]
Message-ID: <1350557230.2460.115.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20121017173119.4e12b222@mantra.us.oracle.com>
On Thu, 2012-10-18 at 01:31 +0100, Mukesh Rathor wrote:
> * the initial domain. For guests using the toolstack, they are in:
> @@ -2177,8 +2210,20 @@ static const struct pv_mmu_ops xen_mmu_ops __initconst = {
>
> void __init xen_init_mmu_ops(void)
> {
> - x86_init.mapping.pagetable_reserve = xen_mapping_pagetable_reserve;
> x86_init.paging.pagetable_init = xen_pagetable_init;
> +
> + if (xen_feature(XENFEAT_auto_translated_physmap)) {
> + pv_mmu_ops.flush_tlb_others = xen_flush_tlb_others;
> +#if 0
I don't recall seeing this #if 0 before -- is it new and/or deliberate?
If it is a marker for future work can we leave it out for now?
> + /* For PCI devices to map iomem. */
> + if (xen_initial_domain()) {
> + pv_mmu_ops.set_pte = native_set_pte;
> + pv_mmu_ops.set_pte_at = native_set_pte_at;
> + }
> +#endif
> + return;
> + }
> + x86_init.mapping.pagetable_reserve = xen_mapping_pagetable_reserve;
> pv_mmu_ops = xen_mmu_ops;
>
next prev parent reply other threads:[~2012-10-18 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 0:31 Mukesh Rathor
2012-10-18 10:47 ` Ian Campbell [this message]
2012-10-18 11:31 ` Stefano Stabellini
2012-10-18 17:12 ` Mukesh Rathor
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=1350557230.2460.115.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.rathor@oracle.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
all inboxes | Powered by JetHome®