public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: Eric Auger <eric.auger@redhat.com>,
	"\"eric.auger.pro"@gmail.com, eric.auger@redhat.com,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
	joro@8bytes.org, alex.williamson@redhat.com,
	jean-philippe.brucker@arm.com, jacob.jun.pan@linux.intel.com,
	"yi.l.liu\""@linux.intel.com, will.deacon@arm.com,
	robin.murphy@arm.com
Cc: marc.zyngier@arm.com, peter.maydell@linaro.org, christoffer.dall@arm.com
Subject: Re: [RFC 09/13] iommu/smmuv3: Get prepared for nested stage support
Date: Fri, 31 Aug 2018 14:20:34 +0100	[thread overview]
Message-ID: <538a2b88-dec5-a6fa-d918-486284eb56a9@arm.com> (raw)
In-Reply-To: <1535026656-8450-10-git-send-email-eric.auger@redhat.com>

On 23/08/18 13:17, Eric Auger wrote:
>  	if (ste->s1_cfg) {
> -		BUG_ON(ste_live);

Scary! :) The current code assumes that it can make modifications to the
STE in any order and enable translation after a sync. So far I haven't
been able to find anything that violates this rule in the spec: "If
software modifies the structure while it is valid, it must not allow the
structure to enter an invalid intermediate state." So maybe it's fine,
though to be safe I would have started with disabling the STE
(http://www.linux-arm.org/git?p=linux-jpb.git;a=commitdiff;h=936e49f923e101c061269eadd5fa43fef819d2e9)

Thanks,
Jean

  parent reply	other threads:[~2018-08-31 13:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1535026656-8450-1-git-send-email-eric.auger@redhat.com>
     [not found] ` <1535026656-8450-2-git-send-email-eric.auger@redhat.com>
2018-08-23 15:25   ` [RFC 01/13] iommu: Introduce bind_guest_stage API Auger Eric
2018-08-31 13:11     ` Jean-Philippe Brucker
     [not found]       ` <b7909f1b-57ce-f4db-d916-140a63283232-5wv7dgnIgG8@public.gmane.org>
2018-08-31 13:52         ` Auger Eric
2018-09-03 12:19           ` Jean-Philippe Brucker
     [not found]           ` <4309832b-27ed-597a-b5a1-f439fbea9843-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-04  7:57             ` Tian, Kevin
2018-09-04  8:10               ` Auger Eric
     [not found]                 ` <220e4c2a-d31c-d8fb-2d77-d902d2f13bb2-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-04  8:34                   ` Tian, Kevin
2018-09-04  8:41                     ` Auger Eric
2018-09-04  8:43                       ` Tian, Kevin
2018-09-04  9:53                       ` Jean-Philippe Brucker
2018-09-05  0:36                         ` Tian, Kevin
     [not found]   ` <A2975661238FB949B60364EF0F2C257439CCE9EE@SHSMSX104.ccr.corp.intel.com>
2018-08-24 13:20     ` Auger Eric
     [not found] ` <1535026656-8450-3-git-send-email-eric.auger@redhat.com>
2018-08-31 13:17   ` [RFC 02/13] iommu: Introduce tlb_invalidate API Jean-Philippe Brucker
2018-08-31 14:07     ` Auger Eric
2018-09-03 12:28       ` Jean-Philippe Brucker
2018-09-03 12:41         ` Auger Eric
2018-09-03 13:41           ` Jean-Philippe Brucker
     [not found] ` <1535026656-8450-10-git-send-email-eric.auger@redhat.com>
2018-08-31 13:20   ` Jean-Philippe Brucker [this message]
2018-08-31 14:11     ` [RFC 09/13] iommu/smmuv3: Get prepared for nested stage support Auger Eric
     [not found]       ` <012d4950-7a06-2d59-85a0-44d511ad893b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-03 12:29         ` Jean-Philippe Brucker
2018-09-03 12:48           ` Auger Eric

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=538a2b88-dec5-a6fa-d918-486284eb56a9@arm.com \
    --to=jean-philippe.brucker@arm.com \
    --cc="\"eric.auger.pro"@gmail.com \
    --cc="yi.l.liu\""@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=christoffer.dall@arm.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=robin.murphy@arm.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox