qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Julien Grall <julien.grall@gmail.com>
Cc: qemu-devel@nongnu.org, Fabien Chouteau <chouteau@adacore.com>
Subject: Re: [Qemu-devel] [PATCH 2/2][SPARC] Fix TA0_Shutdown feature
Date: Fri, 20 May 2011 19:03:53 +0300	[thread overview]
Message-ID: <BANLkTin1nSNG42a8XEt78f3GYHh5xuv5OA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin0GrKea_XwnWn7MUHK_LTLTD9E7A@mail.gmail.com>

On Wed, May 18, 2011 at 4:17 PM, Julien Grall <julien.grall@gmail.com> wrote:
> On Tue, May 17, 2011 at 9:57 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Tue, May 17, 2011 at 6:32 PM, Julien Grall <julien.grall@gmail.com> wrote:
>>> Fix TA0_SHUTDOWN feature
>>
>> But what would be the bug?
>
> We try to add RTEMS's support on leon platform for QEMU. RTEMS uses
> software trap 0 for various syscall.
> The current implementation of TA0_SHUTDOWN breaks the RTEMS boot.
>
>> No, this would actually be just opposite to how QEMU works.
>> Performance comes from doing more work at translation time in order to
>> save time during executing the generated code.
>
> I agree, this solution slows down the execution, but I didn't find
> another solution to fix this bug.

You should retain the feature check in translate.c but add a leon
specific helper in place of helper_shutdown, which can check for
psret.

It would be also possible to generate code for the psret check if the
helper overhead were an issue.

      reply	other threads:[~2011-05-20 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTikeSfsp537pf-unOyR4ftxctmfP2w@mail.gmail.com>
2011-05-17 15:32 ` [Qemu-devel] [PATCH 2/2][SPARC] Fix TA0_Shutdown feature Julien Grall
2011-05-17 19:57   ` Blue Swirl
2011-05-18 13:17     ` Julien Grall
2011-05-20 16:03       ` Blue Swirl [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=BANLkTin1nSNG42a8XEt78f3GYHh5xuv5OA@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=chouteau@adacore.com \
    --cc=julien.grall@gmail.com \
    --cc=qemu-devel@nongnu.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).