From: Tim Deegan <tim@xen.org>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: [PATCH] nestedhvm: avoid endless loop of nested page faults
Date: Fri, 19 Aug 2011 13:46:21 +0100 [thread overview]
Message-ID: <20110819124621.GD25206@ocelot.phlegethon.org> (raw)
In-Reply-To: <4E4E50D1.2050001@amd.com>
At 14:02 +0200 on 19 Aug (1313762545), Christoph Egger wrote:
> Stop sending IPIs to flush the nested-on-nested pagetable
> after write operations. Instead flush the TLB only.
> This fixes an endless loop of nested page faults after
> adding an entry to the nested-on-nested pagetable.
>
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
Applied, thanks.
Tim.
--
Tim Deegan <tim@xen.org>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
prev parent reply other threads:[~2011-08-19 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 12:02 [PATCH] nestedhvm: avoid endless loop of nested page faults Christoph Egger
2011-08-19 12:46 ` Tim Deegan [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=20110819124621.GD25206@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Christoph.Egger@amd.com \
--cc=Tim.Deegan@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).