From: John Snow <jsnow@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/8] ahci: MSI capability should be at 0x80, not 0x50.
Date: Wed, 17 Sep 2014 12:42:33 -0400 [thread overview]
Message-ID: <5419B9F9.3080008@redhat.com> (raw)
In-Reply-To: <20140917164243.GA19133@redhat.com>
On 09/17/2014 12:42 PM, Michael S. Tsirkin wrote:
> On Wed, Sep 17, 2014 at 05:54:28PM +0200, Jan Kiszka wrote:
>> On 2014-08-21 19:44, John Snow wrote:
>>> In the Intel ICH9 data sheet, the MSI capability offset
>>> in the PCI configuration space for ICH9 AHCI devices is
>>> specified to be 0x80.
>>>
>>> Further, the PCI capability pointer should always point
>>> to 0x80 in ICH9 devices, despite the fact that AHCI 1.3
>>> specifies that it should be pointing to PMCAP (Which in
>>> this instance would be 0x70) to maintain adherence to
>>> the Intel data sheet specifications and real observed behavior.
>>>
>>> Signed-off-by: John Snow <jsnow@redhat.com>
>>> ---
>>> hw/ide/ich.c | 7 ++++++-
>>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/hw/ide/ich.c b/hw/ide/ich.c
>>> index a2f1639..8eb77a1 100644
>>> --- a/hw/ide/ich.c
>>> +++ b/hw/ide/ich.c
>>> @@ -71,6 +71,7 @@
>>> #include <hw/ide/pci.h>
>>> #include <hw/ide/ahci.h>
>>>
>>> +#define ICH9_MSI_CAP_OFFSET 0x80
>>> #define ICH9_SATA_CAP_OFFSET 0xA8
>>>
>>> #define ICH9_IDP_BAR 4
>>> @@ -115,7 +116,6 @@ static int pci_ich9_ahci_init(PCIDevice *dev)
>>> /* XXX Software should program this register */
>>> dev->config[0x90] = 1 << 6; /* Address Map Register - AHCI mode */
>>>
>>> - msi_init(dev, 0x50, 1, true, false);
>>> d->ahci.irq = pci_allocate_irq(dev);
>>>
>>> pci_register_bar(dev, ICH9_IDP_BAR, PCI_BASE_ADDRESS_SPACE_IO,
>>> @@ -135,6 +135,11 @@ static int pci_ich9_ahci_init(PCIDevice *dev)
>>> (ICH9_IDP_BAR + 0x4) | (ICH9_IDP_INDEX_LOG2 << 4));
>>> d->ahci.idp_offset = ICH9_IDP_INDEX;
>>>
>>> + /* Although the AHCI 1.3 specification states that the first capability
>>> + * should be PMCAP, the Intel ICH9 data sheet specifies that the ICH9
>>> + * AHCI device puts the MSI capability first, pointing to 0x80. */
>>> + msi_init(dev, ICH9_MSI_CAP_OFFSET, 1, true, false);
>>> +
>>> return 0;
>>> }
>>>
>>>
>>
>> I did this for HDA recently, and it became clear that this requires a
>> compat switch to expose the old, broken layout to older guests.
>> Otherwise you can't migrate from them.
>>
>> Jan
>
> Absolutely but ahci still disables migration :)
I was halfway to preparing a v5, but you're right ... We've disabled
AHCI migration until we iron out the most egregious kinks.
>
>> --
>> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
>> Corporate Competence Center Embedded Linux
--
—js
next prev parent reply other threads:[~2014-09-17 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 17:44 [Qemu-devel] [PATCH v4 0/8] AHCI test suite framework John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 1/8] ahci: Adding basic functionality qtest John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 2/8] ahci: MSI capability should be at 0x80, not 0x50 John Snow
2014-09-17 15:54 ` Jan Kiszka
2014-09-17 16:42 ` Michael S. Tsirkin
2014-09-17 16:42 ` John Snow [this message]
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 3/8] ahci: Add test_pci_spec to ahci-test John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 4/8] ahci: add test_pci_enable " John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 5/8] ahci: properly shadow the TFD register John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 6/8] ahci: Add test_hba_spec to ahci-test John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 7/8] ahci: Add test_hba_enable " John Snow
2014-08-21 17:44 ` [Qemu-devel] [PATCH v4 8/8] ahci: Add test_identify case " John Snow
2014-09-09 17:16 ` [Qemu-devel] [PATCH v4 0/8] AHCI test suite framework John Snow
2014-09-09 20:56 ` Michael S. Tsirkin
2014-09-17 15:15 ` Stefan Hajnoczi
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=5419B9F9.3080008@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).