From: Juan Quintela <quintela@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] Add support for async page fault to qemu
Date: Mon, 18 Oct 2010 17:48:16 +0200 [thread overview]
Message-ID: <m3k4lf5wov.fsf@trasno.mitica> (raw)
In-Reply-To: <20101018132538.GC10207@redhat.com> (Gleb Natapov's message of "Mon, 18 Oct 2010 15:25:38 +0200")
Gleb Natapov <gleb@redhat.com> wrote:
> Add save/restore of MSR for migration and cpuid bit.
It is there a way to test if async page faults are in use?
if so, we can add a subsection instead of changing the cpuversion.
I think that at some point we are going to need a bitmap that indicates
what MSR's have been used or something like that.
What do you think?
Later, Juan.
next prev parent reply other threads:[~2010-10-18 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 13:25 [PATCH] Add support for async page fault to qemu Gleb Natapov
2010-10-18 15:48 ` Juan Quintela [this message]
2010-10-18 15:53 ` Avi Kivity
2010-10-18 16:29 ` Gleb Natapov
2010-10-21 15:08 ` [PATCHv2] " Gleb Natapov
2010-10-21 16:03 ` Marcelo Tosatti
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=m3k4lf5wov.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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