From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53761] nVMX: MSR bitmap merging
Date: Mon, 25 Feb 2013 13:59:58 +0000 (UTC) [thread overview]
Message-ID: <20130225135958.7C0F411FB5A@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-53761-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=53761
--- Comment #1 from Nadav Har'El <nyh@math.technion.ac.il> 2013-02-25 13:59:58 ---
The same technique, and code, can be reused also for merging of IO bitmaps.
This will offer less of a performance impact than that on MSR bitmaps, because
the KVM L0 anyway wants exit on all IO ports (except the esoteric port 0x80
used for delays). So I am guessing no performance improvement will be seen
because of merging IO bitmaps.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-02-25 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 9:38 [Bug 53761] New: nVMX: MSR bitmap merging bugzilla-daemon
2013-02-13 9:39 ` [Bug 53761] " bugzilla-daemon
2013-02-25 13:59 ` bugzilla-daemon [this message]
2015-03-17 3:53 ` bugzilla-daemon
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=20130225135958.7C0F411FB5A@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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