From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v2 10/12] xen/iommu: smmu: Check for duplicate stream IDs when registering master devices Date: Tue, 27 Jan 2015 17:33:56 +0000 Message-ID: <54C7CC04.9000509@linaro.org> References: <1421418247-30068-1-git-send-email-julien.grall@linaro.org> <1421418247-30068-11-git-send-email-julien.grall@linaro.org> <54C7C263.7090806@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YGA1y-000342-9X for xen-devel@lists.xenproject.org; Tue, 27 Jan 2015 17:34:26 +0000 Received: by mail-wi0-f174.google.com with SMTP id n3so6497758wiv.1 for ; Tue, 27 Jan 2015 09:34:24 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: ian.campbell@citrix.com, tim@xen.org, Andreas Herrmann , stefano.stabellini@citrix.com, Andreas Herrmann , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On 27/01/15 17:02, Stefano Stabellini wrote: > On Tue, 27 Jan 2015, Julien Grall wrote: >> On 27/01/15 16:30, Stefano Stabellini wrote: >>> On Fri, 16 Jan 2015, Julien Grall wrote: >>>> From: Andreas Herrmann >>>> >>>> If DT information lists one stream ID twice for the master devices of >>>> an SMMU this can cause a multi match when stream ID matching is used. >>>> For stream ID indexing this might trigger an overwrite of an S2CR that >>>> is already in use. >>>> >>>> So better check for duplicates when DT information is parsed. >>>> >>>> Taken from the linux ML: >>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-January/226099.html >>>> >>>> Cc: Andreas Herrmann >>>> Signed-off-by: Andreas Herrmann >>>> Signed-off-by: Julien Grall >>> >>> Why didn't you just take a more recent version of the Linux smmu driver? >> >> The SMMU driver very is recent (see commit in the previous patch)... >> Just this patch has never reached upstream. > > That is not good. It might be worth to wait for it to go upstream. The patch was sent one year ago. Just before Calxeda was shutdown. This is a requirement for the following patch. Do you think the other patch should be upstream to Linux before? If so, Calxeda server won't be able to use properly SMMU. Even though the server will never be used, I do all my SMMU development on it. FWIW, we use already use the 2 patches in the current SMMU drivers. Regards, -- Julien Grall