From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/mm changes for v3.9-rc1
Date: Sat, 23 Feb 2013 14:43:01 -0500 [thread overview]
Message-ID: <20130223194300.GA13174@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <CAE9FiQUcJiDOjv-XYYUfQAAHaZCq2Q1heR5YakGf13SYJjxyxA@mail.gmail.com>
> >> how about if we call load_cr3 early several times?
> >> assume you should make xen_write_cr3 more robust,
> >> like bailing out early when cr3 writing same value.
> >
> > I would welcome such patch - but at this point I just want a
> > patch for Linus so that I am not blocking him - and this
> > one works.
>
> come on, you produce
>
> #ifdef CONFIG_X86_32
> .write_cr3 = xen_write_cr3_init,
> #else
> .write_cr3 = xen_write_cr3_init,
> #endif
>
> for the fix, Linus should just apply attached patch instead.
I misunderstood you. I thought you were talking about
"how about if we call .. cr3 writing same value" - and that part
I hadn't thought completly through so I did not want to delay
Linus.
Naturally the fixes you pointed out should be in the patch - and
hpa graciously did the fixes and sent to Linus. Thank you Peter!
>
> >>
> >> Also you should check condition about calling xen_get_user_pgd().
> >
> > Could you elaborate please?
>
> only call xen_get_user_pgd() when it should be called.
I should have been more explicit. When I was saying "elaborate" I was
soliciting for advice on the 'check condition' and how to make it robust.
>
> Yinghai
next prev parent reply other threads:[~2013-02-23 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAE9FiQX5r02Prsw-f0HsgLVJ0FZeYL9aggXebwWR-E5oYsj6cw@mail.gmail.com>
[not found] ` <5127C620.2040605@linux.intel.com>
[not found] ` <alpine.DEB.2.02.1302221929040.22997@kaball.uk.xensource.com>
[not found] ` <5127CE65.5010703@linux.intel.com>
[not found] ` <CAE9FiQXHHFb0W+aJCsefRNj4p+X1+m8JOLUDz74w-nAjnhym+A@mail.gmail.com>
[not found] ` <5127DDB3.2010309@zytor.com>
[not found] ` <CAE9FiQWctM60VwXJYtOXwPBNLUoz966Fr1g6MPsPoJBiye88YQ@mail.gmail.com>
[not found] ` <5127FBA4.1040506@zytor.com>
[not found] ` <20130223003738.GA23545@phenom.dumpdata.com>
[not found] ` <CAE9FiQVTbDkvU8KQGVoYv3kn6UeCTcdiPA2hvw21OKtNbM=XKg@mail.gmail.com>
[not found] ` <20130223012716.GA28377@phenom.dumpdata.com>
2013-02-23 1:39 ` Yinghai Lu
2013-02-23 19:43 ` Konrad Rzeszutek Wilk [this message]
2013-02-23 21:37 ` Yinghai Lu
2013-02-23 21:42 ` H. Peter Anvin
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=20130223194300.GA13174@konrad-lan.dumpdata.com \
--to=konrad@kernel.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/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®