On Wed, Nov 13, 2019 at 12:05 AM Joerg Roedel wrote:
>
> On Tue, Nov 12, 2019 at 05:32:31PM +0800, Huang Adrian wrote:
> > > On Mon, Nov 11, 2019 at 11:22 PM Joerg Roedel wrote:
>
> > > So there are a couple of options here:
> > >
> > > 1) Bail out and disable the IOMMU as the BIOS
On Tue, Nov 12, 2019 at 05:32:31PM +0800, Huang Adrian wrote:
> > On Mon, Nov 11, 2019 at 11:22 PM Joerg Roedel wrote:
> > So there are a couple of options here:
> >
> > 1) Bail out and disable the IOMMU as the BIOS screwed up
> >
> > 2) Treat per-device exclusion ranges just as
Hi Joerg,
> On Mon, Nov 11, 2019 at 11:22 PM Joerg Roedel wrote:
>
> Hi Adrian,
>
> On Mon, Nov 04, 2019 at 01:58:52PM +0800, Adrian Huang wrote:
> > 2) When set_device_exclusion_range() parses the IVMD of devce id
> > '4200', the exclusion range of the amd_iommu struct becomes:
>
Hi Adrian,
On Mon, Nov 04, 2019 at 01:58:52PM +0800, Adrian Huang wrote:
> 2) When set_device_exclusion_range() parses the IVMD of devce id
> '4200', the exclusion range of the amd_iommu struct becomes:
>
> iommu->exclusion_start = 0x9F58D000;
>
When attaching two Broadcom RAID controllers to a server, the first one
reports the failure during booting (the disks connecting to the RAID
controller cannot be detected):
megaraid_sas :42:00.0: Init cmd return status FAILED for SCSI host 0
megaraid_sas :42:00.0: Failed from
