All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe DUBOIS <jcd@tribudubois.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, xvisor-devel@googlegroups.com
Subject: Re: [Qemu-devel] [PATCH v2] arm: Fix CP15 FSR (C5) domain setting
Date: Sun, 06 Nov 2011 18:45:16 +0100	[thread overview]
Message-ID: <4EB6C7AC.9070100@tribudubois.net> (raw)
In-Reply-To: <CAFEAcA_rhEn_gyNAoJyjkv8exDPDQV9UBo=NsgrL6zXcpVzhQA@mail.gmail.com>

On 06/11/2011 18:33, Peter Maydell wrote:
> On 5 November 2011 11:42, Jean-Christophe DUBOIS<jcd@tribudubois.net>  wrote:
>> During Xvisor development, it was noted that qemu did not return
>> the correct domain value in the Cp15 [Data] FSR register (C5).
>>
>> This patch is a proposal to fix it.
>>
>> v2:
>> - fix coding style
>> - rebase on git.
>>
>> Signed-off-by: Jean-Christophe DUBOIS<jcd@tribudubois.net>
>
> Reviewed-by: Peter Maydell<peter.maydell@linaro.org>
>
> NB: not going to put this into 1.0, it's a bit late and it's not
> a critical bug fix IMHO. In particular, well behaved code shouldn't
> be relying on this DFSR field; see the ARM ARM B3.9.7:
> "From ARMv7, use of the domain field in the DFSR is deprecated. This
> field might not be supported in future versions of the ARM architecture.
> ARM strongly recommends that new software does not use this field."
Yes, same comment from the xvisor side of things. As xvisor targets 
mainly ARMv7 (and MIPS) for now, this was not a real issue.

Nonetheless this is worth fixing at some point in time (but this can be 
post 1.0).

JC
>
>
> -- PMM
>

      reply	other threads:[~2011-11-06 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05 11:42 [Qemu-devel] [PATCH v2] arm: Fix CP15 FSR (C5) domain setting Jean-Christophe DUBOIS
2011-11-06 17:33 ` Peter Maydell
2011-11-06 17:45   ` Jean-Christophe DUBOIS [this message]

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=4EB6C7AC.9070100@tribudubois.net \
    --to=jcd@tribudubois.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xvisor-devel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.