All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@amd.com>,
	xen-devel <xen-devel@lists.xen.org>,
	suravee.suthikulpanit@amd.com,
	Sherry Hurwitz <sherry.hurwitz@amd.com>
Subject: Re: [PATCH 1/2] AMD IOMMU: also spot missing IO-APIC entries in IVRS table
Date: Tue, 12 Feb 2013 11:59:08 +0000	[thread overview]
Message-ID: <511A3C9C02000078000BDB53@nat28.tlf.novell.com> (raw)
In-Reply-To: <1360579774.29432.102.camel@zakaz.uk.xensource.com>

>>> On 11.02.13 at 11:49, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2013-02-06 at 13:12 +0000, Jan Beulich wrote:
>> Apart from dealing duplicate conflicting entries, we also have to
>> handle firmware omitting IO-APIC entries in IVRS altogether. Not doing
>> so has resulted in c/s 26517:601139e2b0db to crash such systems during
>> boot (whereas with the change here the IOMMU gets disabled just as is
>> being done in the other cases, i.e. unless global tables are being
>> used).
>> 
>> Debugging this issue has also pointed out that the debug log output is
>> pretty ugly to look at - consolidate the output, and add one extra
>> item for the IVHD special entries, so that future issues are easier
>> to analyze.
>> 
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> Tested-by: Sander Eikelenboom <linux@eikelenboom.it>
> 
> Not really my area but the change looks reasonably straight forward and
> fixes a real error observed in the field,
> Acked-by: Ian Campbell <ian.campbell@citrix.com>

While I'd like to see this one go in rather sooner than later, I'm
willing to wait for the community call tomorrow to see whether
we can get an AMD side ack for this and the other patch. But
we surely shouldn't defer getting this in for much longer.

Jan

>> --- a/xen/drivers/passthrough/amd/iommu_acpi.c
>> +++ b/xen/drivers/passthrough/amd/iommu_acpi.c
>> @@ -354,9 +354,8 @@ static int __init parse_ivmd_block(const
>>      base = start_addr & PAGE_MASK;
>>      limit = (start_addr + mem_length - 1) & PAGE_MASK;
>>  
>> -    AMD_IOMMU_DEBUG("IVMD Block: Type %#x\n",ivmd_block->header.type);
>> -    AMD_IOMMU_DEBUG(" Start_Addr_Phys %#lx\n", start_addr);
>> -    AMD_IOMMU_DEBUG(" Mem_Length %#lx\n", mem_length);
>> +    AMD_IOMMU_DEBUG("IVMD Block: type %#x phys %#lx len %#lx\n",
>> +                    ivmd_block->header.type, start_addr, mem_length);
>>  
>>      if ( ivmd_block->header.flags & ACPI_IVMD_EXCLUSION_RANGE )
>>          iw = ir = IOMMU_CONTROL_ENABLED;
>> @@ -551,8 +550,8 @@ static u16 __init parse_ivhd_device_alia
>>          return 0;
>>      }
>>  
>> -    AMD_IOMMU_DEBUG(" Dev_Id Range: %#x -> %#x\n", first_bdf, last_bdf);
>> -    AMD_IOMMU_DEBUG(" Dev_Id Alias: %#x\n", alias_id);
>> +    AMD_IOMMU_DEBUG(" Dev_Id Range: %#x -> %#x alias %#x\n",
>> +                    first_bdf, last_bdf, alias_id);
>>  
>>      for ( bdf = first_bdf; bdf <= last_bdf; bdf++ )
>>          add_ivrs_mapping_entry(bdf, alias_id, 
> range->alias.header.data_setting,
>> @@ -654,6 +653,9 @@ static u16 __init parse_ivhd_device_spec
>>          return 0;
>>      }
>>  
>> +    AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle 
> %#x\n",
>> +                    seg, PCI_BUS(bdf), PCI_SLOT(bdf), PCI_FUNC(bdf),
>> +                    special->variety, special->handle);
>>      add_ivrs_mapping_entry(bdf, bdf, special->header.data_setting, iommu);
>>  
>>      switch ( special->variety )
>> @@ -758,10 +760,9 @@ static int __init parse_ivhd_block(const
>>      {
>>          ivhd_device = (const void *)((const u8 *)ivhd_block + 
> block_length);
>>  
>> -        AMD_IOMMU_DEBUG( "IVHD Device Entry:\n");
>> -        AMD_IOMMU_DEBUG( " Type %#x\n", ivhd_device->header.type);
>> -        AMD_IOMMU_DEBUG( " Dev_Id %#x\n", ivhd_device->header.id);
>> -        AMD_IOMMU_DEBUG( " Flags %#x\n", ivhd_device->header.data_setting);
>> +        AMD_IOMMU_DEBUG("IVHD Device Entry: type %#x id %#x flags %#x\n",
>> +                        ivhd_device->header.type, ivhd_device->header.id,
>> +                        ivhd_device->header.data_setting);
>>  
>>          switch ( ivhd_device->header.type )
>>          {
>> @@ -890,6 +891,7 @@ static int __init parse_ivrs_table(struc
>>  {
>>      const struct acpi_ivrs_header *ivrs_block;
>>      unsigned long length;
>> +    unsigned int apic;
>>      int error = 0;
>>  
>>      BUG_ON(!table);
>> @@ -903,11 +905,9 @@ static int __init parse_ivrs_table(struc
>>      {
>>          ivrs_block = (struct acpi_ivrs_header *)((u8 *)table + length);
>>  
>> -        AMD_IOMMU_DEBUG("IVRS Block:\n");
>> -        AMD_IOMMU_DEBUG(" Type %#x\n", ivrs_block->type);
>> -        AMD_IOMMU_DEBUG(" Flags %#x\n", ivrs_block->flags);
>> -        AMD_IOMMU_DEBUG(" Length %#x\n", ivrs_block->length);
>> -        AMD_IOMMU_DEBUG(" Dev_Id %#x\n", ivrs_block->device_id);
>> +        AMD_IOMMU_DEBUG("IVRS Block: type %#x flags %#x len %#x id %#x\n",
>> +                        ivrs_block->type, ivrs_block->flags,
>> +                        ivrs_block->length, ivrs_block->device_id);
>>  
>>          if ( table->length < (length + ivrs_block->length) )
>>          {
>> @@ -922,6 +922,29 @@ static int __init parse_ivrs_table(struc
>>          length += ivrs_block->length;
>>      }
>>  
>> +    /* Each IO-APIC must have been mentioned in the table. */
>> +    for ( apic = 0; !error && apic < nr_ioapics; ++apic )
>> +    {
>> +        if ( !nr_ioapic_entries[apic] ||
>> +             ioapic_sbdf[IO_APIC_ID(apic)].pin_setup )
>> +            continue;
>> +
>> +        printk(XENLOG_ERR "IVHD Error: no information for IO-APIC %#x\n",
>> +               IO_APIC_ID(apic));
>> +        if ( amd_iommu_perdev_intremap )
>> +            error = -ENXIO;
>> +        else
>> +        {
>> +            ioapic_sbdf[IO_APIC_ID(apic)].pin_setup = xzalloc_array(
>> +                unsigned long, BITS_TO_LONGS(nr_ioapic_entries[apic]));
>> +            if ( !ioapic_sbdf[IO_APIC_ID(apic)].pin_setup )
>> +            {
>> +                printk(XENLOG_ERR "IVHD Error: Out of memory\n");
>> +                error = -ENOMEM;
>> +            }
>> +        }
>> +    }
>> +
>>      return error;
>>  }
>>  
>> 
>> 

  reply	other threads:[~2013-02-12 11:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 13:04 [PATCH 0/2] AMD IOMMU: XSA-36 follow ups Jan Beulich
2013-02-06 13:12 ` [PATCH 1/2] AMD IOMMU: also spot missing IO-APIC entries in IVRS table Jan Beulich
2013-02-06 14:41   ` Boris Ostrovsky
2013-02-06 14:52     ` Jan Beulich
2013-02-06 15:03       ` Boris Ostrovsky
2013-02-06 15:12         ` Jan Beulich
2013-02-11 10:49   ` Ian Campbell
2013-02-12 11:59     ` Jan Beulich [this message]
2013-02-06 13:12 ` [PATCH 2/2] AMD IOMMU: handle MSI for phantom functions Jan Beulich
2013-02-11 10:53   ` Ian Campbell
2013-02-08  9:58 ` [PATCH 0/2] AMD IOMMU: XSA-36 follow ups Jan Beulich
2013-02-08 13:53   ` Sander Eikelenboom
2013-03-01 18:45   ` Malcolm Crossley
2013-03-04  9:48     ` Jan Beulich
2013-02-11 13:12 ` Ian Campbell
2013-02-12  8:45   ` Jan Beulich

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=511A3C9C02000078000BDB53@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=boris.ostrovsky@amd.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xen.org \
    /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.