xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"open list:X86" <xen-devel@lists.xenproject.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH] xen/arm: Warn user on cpu errata 832075
Date: Wed, 21 Oct 2020 09:52:31 +0000	[thread overview]
Message-ID: <3603E591-0936-4D2B-B310-8236AD4DCD7E@arm.com> (raw)
In-Reply-To: <1cd355a4-9907-1596-44d3-d524618e4a35@xen.org>



> On 21 Oct 2020, at 10:46, Julien Grall <julien@xen.org> wrote:
> 
> Hi Bertrand,
> 
> On 21/10/2020 10:44, Bertrand Marquis wrote:
>>> Bertrand reminded me today that I forgot to answer the e-mail (sorry). I am happy with using printk_once().
>> Shall i also keep the .enable implementation ?
>> At the end having:
>>  if ( cpus_have_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE) )
>> in enable_errata_workarounds is quite clean.
> 
> You can pick the one you prefer :).

Thanks, I will push a v2 shortly.

Cheers
Bertrand



  reply	other threads:[~2020-10-21  9:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 10:41 [PATCH] xen/arm: Warn user on cpu errata 832075 Bertrand Marquis
2020-10-14 11:11 ` Julien Grall
2020-10-14 16:00   ` Bertrand Marquis
2020-10-14 20:46     ` Stefano Stabellini
2020-10-14 11:35 ` Andrew Cooper
2020-10-14 16:03   ` Bertrand Marquis
2020-10-14 17:22     ` Julien Grall
2020-10-14 21:15       ` Stefano Stabellini
2020-10-15 10:10         ` Bertrand Marquis
2020-10-15 18:05           ` Stefano Stabellini
2020-10-21  9:03             ` Julien Grall
2020-10-21  9:44               ` Bertrand Marquis
2020-10-21  9:46                 ` Julien Grall
2020-10-21  9:52                   ` Bertrand Marquis [this message]
2020-10-14 17:13   ` Julien Grall

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=3603E591-0936-4D2B-B310-8236AD4DCD7E@arm.com \
    --to=bertrand.marquis@arm.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).