All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: ja <pavel@netsafe.cz>,
	xen-devel@lists.xensource.com, tom.goetz@virtualcomputer.com,
	"Ben Guthro" <ben.guthro@virtualcomputer.com>
Subject: Re: ioperm problem
Date: Thu, 17 Nov 2011 10:05:57 -0800	[thread overview]
Message-ID: <4EC54D05.3050308@goop.org> (raw)
In-Reply-To: <20111117173010.GA3623@phenom.dumpdata.com>

On 11/17/2011 09:30 AM, Konrad Rzeszutek Wilk wrote:
> On Thu, Nov 17, 2011 at 08:56:34AM -0500, Ben Guthro wrote:
>> Attached is our patch to work around issues with the ioports with
>> some older nVidia cards.
>>
>> This, admittedly is a bit of a hack, and not exactly something that
>> I would see upstream wanting to carry, for a variety of reasons. It
>> really should all be predicated on whether the kernel is the initial
>> domain, etc.
>>
>> This opens up the legacy VGA ports in the VGA arbiter code.
> Was there a userspace program that did this? As in it would
> call ioperm?
>
>> Konrad - I think that you had suggested an alternate way of doing
>> this, IIRC, but I can't seem to find it in my inbox. Due to
>> competing demands, and my nVidia hardware disappearing, I never went
>> back to rework this code.
> Ah, I might have some code that I just uncovered from Jeremy's old
> git tree.
>
> I've put it up on devel/ioperm - it nicely wraps the ioperm
> call to go the native or paravirt.

Yeah, I'd sort of let that sit, since there's nothing in a "modern"
system which should require it.  Allowing usermode to poke at ioports
from within a domain is inherently suspect, after all.

    J

  parent reply	other threads:[~2011-11-17 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13 21:19 ioperm problem Pavel Matěja
2011-11-16 14:57 ` Konrad Rzeszutek Wilk
2011-11-17 13:56   ` Ben Guthro
2011-11-17 17:30     ` Konrad Rzeszutek Wilk
2011-11-17 17:37       ` Alan Cox
2011-11-17 18:05       ` Jeremy Fitzhardinge [this message]
2011-11-17 20:29         ` Konrad Rzeszutek Wilk
2011-11-17 22:20         ` Ben Guthro
2011-11-18  8:13       ` Pavel Matěja

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=4EC54D05.3050308@goop.org \
    --to=jeremy@goop.org \
    --cc=ben.guthro@virtualcomputer.com \
    --cc=konrad.wilk@oracle.com \
    --cc=pavel@netsafe.cz \
    --cc=tom.goetz@virtualcomputer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.