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

Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx


  • To: Roman Shaposhnik <roman@xxxxxxxxxx>
  • From: Jan Beulich <JBeulich@xxxxxxxx>
  • Date: Wed, 31 Jul 2019 08:34:18 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=suse.com;dmarc=pass action=none header.from=suse.com;dkim=pass header.d=suse.com;arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SLvuiN5JTlIPk8wKRs8xgItEVVFvzgzz1LTaeqQkYkY=; b=ejoyrVlbpMXkKZX0zUAUY7qK9lTpMvARTAfX5+j3xo4AMHmUVuOdjIGKOchyDRQddnBZdWXbidCvY6uK5CKqR6egcc12qz8eE0HV/QuCz1pfJr5FHDY0OEZEoFgJ1SKz+8ZquWACWE0WWf0ldSNYgIsHYzp13Ed2S8xYqZBA6KKi+UrhVF1goYqgjp2+PNEXxGmPVXLRsuefqzDSe71g5K3ueVhIOt7w1PCqkonrtDzuwBpAlGmAZhHuCxyCaD+ezkZ0FcR/ZGIazoZwSBmM3OF8qNfpWqeU8Ua866+28vSX2/Pkg4jkfp1OrA27KB2j6medbFRuB7mLRUr4hWodTQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aEX9LDBpDq+ADRFm2X8ZLIfQaX2v+3qiD5UTGBi1fMShoyztD6mRAayJuTrbRo6kLl5ou+eRjhzzDsEd0ls1h0P3fCURB1NpKx8JxWkeUXLjeO/S9OFD4mGTt1hBuRSbxvR7ThY19AncEkPqxDafRQ8fVZoFjqSQdQ9cpFEgv5DVcKgZdZeE94G+FHJRN78yEYguou9Fxpbh5v86NSyw+y8vW+9RVC0d0bitcRQoPDk+SbjymLjMikafjIAbrgCQarz5lZrldFYiEMJD/ECPXIxsS8V9kqBKHOvLxdV4RMwUyglL51mOddQnA9KQOAG9fYmfj5YJBST8ZTdqr0iEaQ==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=JBeulich@xxxxxxxx;
  • Cc: Juergen Gross <JGross@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Paul Durrant <Paul.Durrant@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "boris.ostrovsky@xxxxxxxxxx" <boris.ostrovsky@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Delivery-date: Wed, 31 Jul 2019 08:51:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHVQGZoAIAkO6cfhESDQvB+1ma7GabWTmUwgAAaH4CAACIW8P///zuAgAAjM0D//+s8gIAAJkZwgAADUt6AAIoGGoAAAwRXgAEppbWAAADYpIAABBtqgAACZwCAAAP3BYAAA38agAQHi4CABvFPpYAA9HeA
  • Thread-topic: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx

On 30.07.2019 19:56, Roman Shaposhnik wrote:
> On Fri, Jul 26, 2019 at 1:06 AM Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>
>> On 23.07.2019 20:25, Roman Shaposhnik wrote:
>>> Interestingly enough, adding iommu_inclusive_mapping=1 AND iommu=debug
>>> booted the system just fine.
>>
>> Btw (I've noticed this only now) - are you saying without "iommu=debug"
>> the box does _not_ boot fine, despite the other option?
> 
> Yes. But it made sense to me since iommu=debug (as per your
> explanation) overwhelms the CPU and I guess adding
> iommu_inclusive_mapping=1 avoids the code path that does it?

I'm afraid I don't follow: My question was whether
"iommu_inclusive_mapping=1" alone would not allow the box to boot.
Without "iommu=debug" there's no excessive logging afaict, no
matter what other IOMMU options you use.

Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.