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

Re: [PATCH v3 0/3] Generic SMMU Bindings


  • To: Stefano Stabellini <sstabellini@xxxxxxxxxx>
  • From: Rahul Singh <Rahul.Singh@xxxxxxx>
  • Date: Wed, 3 Feb 2021 17:14:45 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.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=zzN44KkCJ3krwqY6/PWdHUONNqbR+L3AonRvJq6pmlA=; b=LX2Jb9ozk3x0+31MiOP1VrD5+QCFjDdULD/css5w/DmVaurk2EBvIlUVaEjHuWJF2XGcKz1juJH4BJbXmnvEj8TsBh5Dww3PFAt8DaUHhFeuN5REs4rKX8IJSNAO4A0pSBfVMSoTRvqAHmvFaKvrPcs3bC8rzir5UH8IHYrpU0HXsPCojBjM2G2gIomFEwnTd7LApF2o9XXBRHyJBkS9roQqxBA6OpGex3DjovDVdE1gfe6UVmbX9HMlGe5bhLKIhSNqOAstnc/8pKWrHG+AywctYrwWaxy6gr6L1kR4VPpLMvkZ3zUx/BuA+kuf3H6C+3SirzlI7OHb+IKMWZOdng==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A7Zg04LMF6akPsGdAXXSuh6UXe1Ms3NYV4JV+Z/wLph+iXjPetip1V+bklbdtK2WjJ3SBLms6+Mm7XbziSwwj41mqJsNSJqkDQT4zY9lugI6fza8pZfjmDzL+Yz6jSsTm1f/UvAkv1/5dhjxfppnomhkLaMNGHSo9Sjpz/GkbQgi9yDEbFbLPI6Vkj1QpyFdHi7DqINV6yjK288EesNoYNYayFRojrssy92kk9YLMhpH2jRilo1CoqHV2mQDu1/deyNuL/mZgd+FbNrLlStG7zi68vrclgeAnE+4WRjJgHLy19FI8xhtITKQXR7lmelEE5H4S3QJyTbfb+n8GYaDmA==
  • Authentication-results-original: kernel.org; dkim=none (message not signed) header.d=none;kernel.org; dmarc=none action=none header.from=arm.com;
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, "Volodymyr_Babchuk@xxxxxxxx" <Volodymyr_Babchuk@xxxxxxxx>, "brian.woods@xxxxxxxxxx" <brian.woods@xxxxxxxxxx>
  • Delivery-date: Wed, 03 Feb 2021 17:15:16 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: kernel.org; dkim=none (message not signed) header.d=none;kernel.org; dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHW9DbnaDtcsjSAAUiKSXHzYBU+iapFEnqAgAAbJICAAYoWgA==
  • Thread-topic: [PATCH v3 0/3] Generic SMMU Bindings

Hello Stefano,

> On 2 Feb 2021, at 5:44 pm, Stefano Stabellini <sstabellini@xxxxxxxxxx> wrote:
> 
> On Tue, 2 Feb 2021, Rahul Singh wrote:
>> Hello Stefano,
>> 
>>> On 26 Jan 2021, at 10:58 pm, Stefano Stabellini <sstabellini@xxxxxxxxxx> 
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> This series introduces support for the generic SMMU bindings to
>>> xen/drivers/passthrough/arm/smmu.c.
>>> 
>>> The last version of the series was
>>> https://marc.info/?l=xen-devel&m=159539053406643
>>> 
>>> I realize that it is late for 4.15 -- I think it is OK if this series
>>> goes in afterwards.
>> 
>> I tested the series on the Juno board it is woking fine.  
>> I found one issue in SMMU driver while testing this series that is not 
>> related to this series but already existing issue in SMMU driver.
>> 
>> If there are more than one device behind SMMU and they share the same 
>> Stream-Id, SMMU driver is creating the new SMR entry without checking the 
>> already configured SMR entry if SMR entry correspond to stream-id is already 
>> configured.  Because of this I observed the stream match conflicts on Juno 
>> board.
>> 
>> (XEN) smmu: /iommu@7fb30000: Unexpected global fault, this could be serious
>> (XEN) smmu: /iommu@7fb30000:         GFSR 0x00000004, GFSYNR0 0x00000006, 
>> GFSYNR1 0x00000000, GFSYNR2 0x00000000
>> 
>> 
>> Below two patches is required to be ported to Xen to fix the issue from 
>> Linux driver.
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/iommu/arm-smmu.c?h=linux-5.8.y&id=1f3d5ca43019bff1105838712d55be087d93c0da
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/iommu/arm-smmu.c?h=linux-5.8.y&id=21174240e4f4439bb8ed6c116cdbdc03eba2126e
> 
> 
> Good catch and thanks for the pointers! Do you have any interest in
> backporting these two patches or should I put them on my TODO list?

Yes I am happy to backport these patches to XEN. 
I will send the patch for review once 4.15 release branch out from master.
 
Regards,
Rahul
> 
> Unrelated to who does the job, we should discuss if it makes sense to
> try to fix the bug for 4.15. The patches don't seem trivial so I am
> tempted to say that it might be best to leave the bug unfixed for 4.15
> and fix it later.




 


Rackspace

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