All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: Scott Wood <scottwood@freescale.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add e500 instructions dcblc, dcbtls and dcbtstl as no-op
Date: Thu, 30 Jun 2011 10:25:31 +0200	[thread overview]
Message-ID: <4E0C32FB.40302@adacore.com> (raw)
In-Reply-To: <20110628112008.31cf6237@schlenkerla.am.freescale.net>

On 28/06/2011 18:20, Scott Wood wrote:
> On Tue, 28 Jun 2011 10:17:39 +0200
> Fabien Chouteau <chouteau@adacore.com> wrote:
> 
>> On 27/06/2011 18:28, Scott Wood wrote:
>>> On Mon, 27 Jun 2011 15:15:55 +0200
>>> Fabien Chouteau <chouteau@adacore.com> wrote:
>>>
>>>> +/* dcbtls */
>>>> +static void gen_dcbtls(DisasContext *ctx)
>>>> +{
>>>> +    /* interpreted as no-op */
>>>> +}
>>>> +
>>>> +/* dcbtstls */
>>>> +static void gen_dcbtstls(DisasContext *ctx)
>>>> +{
>>>> +    /* interpreted as no-op */
>>>> +}
>>>
>>> Set L1CSR0[CUL] (unable to lock)?
>>
>> Why do you want to set this bit? Can't we consider that the instruction is
>> always effective?
> 
> But it's not.  Why claim it is, in the absence of some specific workload
> that needs to be fooled (which could take many different forms, not all of
> which are appropriate defaults)?

Reading the e500 manual again, it's not clear to me what can make the
L1CSR0[CUL] to be set. If you have a better understanding, can you please
explain?

-- 
Fabien Chouteau

  reply	other threads:[~2011-06-30  8:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 13:15 [Qemu-devel] [PATCH] Add e500 instructions dcblc, dcbtls and dcbtstl as no-op Fabien Chouteau
2011-06-27 16:28 ` Scott Wood
2011-06-28  8:17   ` Fabien Chouteau
2011-06-28 16:20     ` Scott Wood
2011-06-30  8:25       ` Fabien Chouteau [this message]
2011-06-30 16:17         ` Scott Wood
2011-06-30 21:34           ` Alexander Graf
2011-06-30 21:46             ` Scott Wood
2011-06-30 21:56               ` Alexander Graf
2011-06-30 22:11                 ` Scott Wood
2011-06-30 22:18                   ` Alexander Graf
2011-06-30 22:23                     ` Scott Wood
2011-06-30 22:28                       ` Alexander Graf
2011-06-30 22:32                         ` Scott Wood
2011-06-30 22:38                           ` Alexander Graf
2011-07-01 14:59                             ` Fabien Chouteau
2011-07-01 15:05                               ` Alexander Graf
2011-07-01 15:39                                 ` Fabien Chouteau
2011-07-01 16:00                                   ` Scott Wood
2011-07-01 16:21                                     ` Fabien Chouteau

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=4E0C32FB.40302@adacore.com \
    --to=chouteau@adacore.com \
    --cc=qemu-devel@nongnu.org \
    --cc=scottwood@freescale.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.