Re: Niagara2 & Could not register hvapi ATU err=-22

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Tushar Dave <tushar.n.dave@xxxxxxxxxx>
Date: Tue, 15 Aug 2017 15:07:35 -0700

> 
> 
> On 08/15/2017 07:42 AM, Meelis Roos wrote:
>> I noticed that on Niagara2, dmesg has a red error about ATU
>> registration:
>> [    4.579231] pci_sun4v: Could not register hvapi ATU err=-22
>> This is preceded by info line
>> [    4.578073] pci_sun4v: Registered hvapi major[1] minor[0]
>> As I understand, there is no ATU on Niagara1 & Niagara2 sun4v
>> platforms,
>> so there is no point in trying to log an error to dmesg in that case?
> You are right.
> IMO, we should not log ATU hvapi registration failure message at
> all. Unlike PCI hvapi, ATU hvapi registration failure is not *hard
> error*.
> Even if ATU hvapi registration fails (on system with ATU or without
> ATU) system continues with legacy IOMMU.
> So I think log message only when ATU is registered successfully.

Please submit this formally.

Thank you.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux