From: Joerg Roedel <joro@8bytes.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: kvm@vger.kernel.org
Subject: Re: I/O port permission bit inheritance between threads
Date: Tue, 21 May 2013 11:50:30 +0200 [thread overview]
Message-ID: <20130521095030.GC7424@8bytes.org> (raw)
In-Reply-To: <20130520142431.5221e2d0@nehalam.linuxnetplumber.net>
Hey Stephen,
On Mon, May 20, 2013 at 02:24:31PM -0700, Stephen Hemminger wrote:
> ioperm() inheritance across threads is different in KVM then when run
> on physical hardware. The following program runs on physical hardware
> but get SEGV under KVM.
>
> It appears that the I/O permission bits are not shared between threads
> in the same way.
Is this specific to SVM or do you see it on VMX too? My first guess
would be that the KVM instruction emulator does not check to
IO-permissions correctly, but that would affect VMX and SVM.
Joerg
next prev parent reply other threads:[~2013-05-21 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 21:24 I/O port permission bit inheritance between threads Stephen Hemminger
2013-05-21 9:50 ` Joerg Roedel [this message]
2013-05-21 10:01 ` Gleb Natapov
2013-05-21 15:27 ` Stephen Hemminger
2013-05-23 9:27 ` Gleb Natapov
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=20130521095030.GC7424@8bytes.org \
--to=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=stephen@networkplumber.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