From: Olaf Hering <olaf@aepfle.de>
To: Liliang <liangx.z.li@intel.com>
Cc: keir@xen.org, jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/HVM: Fixed the bug which cause the nested hvm guest fail to boot
Date: Mon, 25 Aug 2014 10:08:05 +0200 [thread overview]
Message-ID: <20140825080805.GA1201@aepfle.de> (raw)
In-Reply-To: <1408360314-25784-1-git-send-email-liangx.z.li@intel.com>
On Mon, Aug 18, Liliang wrote:
> From: Li Liang <liangx.z.li@intel.com>
>
> The function memory_type_changed should not be called in hvm_set_guest_pat.
> or the cache will be flushed excessively and make the nested guest very slowly,
> just like blocked.
The patch subject is wrongly worded, it will cause bogus 'git log --oneline' output.
I'm sure there are several bugs which cause nested guests to fail.
Olaf
next prev parent reply other threads:[~2014-08-25 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 11:11 [PATCH] x86/HVM: Fixed the bug which cause the nested hvm guest fail to boot Liliang
2014-08-18 11:26 ` Andrew Cooper
2014-08-18 13:08 ` Jan Beulich
2014-08-18 13:31 ` Jan Beulich
2014-08-25 8:08 ` Olaf Hering [this message]
2014-08-25 8:11 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 2:32 Liliang
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=20140825080805.GA1201@aepfle.de \
--to=olaf@aepfle.de \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=liangx.z.li@intel.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).