From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [RFC][PATCH] pci-assign: Drop support for raw ioport access
Date: Tue, 29 May 2012 12:26:31 +0300
Message-ID: <4FC49647.2020805@redhat.com>
References: <4FC377AD.8060201@web.de> <4FC38659.8090309@redhat.com> <4FC47F28.3040008@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Alex Williamson <alex.williamson@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:49229 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752228Ab2E2J0f (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 29 May 2012 05:26:35 -0400
In-Reply-To: <4FC47F28.3040008@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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?




-- 
error compiling committee.c: too many arguments to function