public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [RFC][PATCH] pci-assign: Drop support for raw ioport access
Date: Tue, 29 May 2012 07:47:59 -0600	[thread overview]
Message-ID: <1338299279.4714.98.camel@ul30vt> (raw)
In-Reply-To: <4FC49647.2020805@redhat.com>

On Tue, 2012-05-29 at 12:26 +0300, Avi Kivity wrote:
> On 05/29/2012 10:47 AM, Jan Kiszka wrote:
> > 
> >> 
> >> Under what conditions would the kernel not support ioport access via sysfs?
> >> 
> > 
> > No clue. The oldest kernel I checked (2.6.16) does not contain traces it
> > would refuse to provide access.
> 
> I guess this was added first, and sysfs support was added later
> (9ed83e8eb18b0).  Alex, any idea what kernels would fail this?

It's more recent than that.  8633328b is where we added pci-sysfs ioport
access, so 2.6.35 would be the first kernel with it.  I don't really
know how this ever worked except for a very limited range of io ports
addresses before the sysfs access went in, so I'm ok with removing it.
Thanks,

Alex




  reply	other threads:[~2012-05-29 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 13:03 [RFC][PATCH] pci-assign: Drop support for raw ioport access Jan Kiszka
2012-05-28 14:06 ` Avi Kivity
2012-05-29  7:47   ` Jan Kiszka
2012-05-29  9:26     ` Avi Kivity
2012-05-29 13:47       ` Alex Williamson [this message]
2012-05-29 14:00         ` Avi Kivity
2012-05-29  9:23 ` [PATCH] qemu-kvm: " Jan Kiszka
2012-05-29 13:51 ` [RFC][PATCH] pci-assign: " Alex Williamson
2012-05-29 14:41 ` Alex Williamson
2012-05-29 15:45   ` Jan Kiszka

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=1338299279.4714.98.camel@ul30vt \
    --to=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox