From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53698)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1YQalx-0003z0-Cs
	for qemu-devel@nongnu.org; Wed, 25 Feb 2015 07:09:02 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1YQals-0006Su-EU
	for qemu-devel@nongnu.org; Wed, 25 Feb 2015 07:09:01 -0500
Received: from cantor2.suse.de ([195.135.220.15]:52029 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1YQals-0006Sb-7N
	for qemu-devel@nongnu.org; Wed, 25 Feb 2015 07:08:56 -0500
Message-ID: <54EDBB56.10205@suse.de>
Date: Wed, 25 Feb 2015 13:08:54 +0100
From: Alexander Graf <agraf@suse.de>
MIME-Version: 1.0
References: <54EC8BE3.703@huawei.com> <54EDBB0A.7020009@huawei.com>
In-Reply-To: <54EDBB0A.7020009@huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] QEMU pci mach-virt: setting PCI_INTERRUPT_LINE?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Claudio Fontana <claudio.fontana@huawei.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>



On 25.02.15 13:07, Claudio Fontana wrote:
> 
> 
> On 24.02.2015 15:34, Claudio Fontana wrote:
>> Hello,
>>
>> I am trying to set the pci interrupt line field in the configuration space
>> (offset 0x3c), since it is initialized as zero.
>>
>> I would like to set it to the right value as read from the device tree,
>> in order for other existing software which relies on it to be able to work unmodified..
>>
>> but it does not seem to work (I seem to read back zero even after setting the PCI_INTERRUPT_LINE field).
>>
>> I am also reading the interrupt pin, but that one instead seems to work out of the box..
>>
>> Thank you for any suggestion,
>>
>> Claudio
> 
> By the way, I am currently just avoiding to rely on PCI_INTERRUPT_LINE for AArch64,
> but shouldn't the register be programmable?

As far as I understand the register should really just be a scratch r/w
register, yeah. Are you sure you're writing in byte granularity?


Alex