From: Blue Swirl <blauwirbel@gmail.com>
To: Igor Kovalenko <igor.v.kovalenko@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc64: trap handling corrections
Date: Sun, 12 Jul 2009 11:53:45 +0300 [thread overview]
Message-ID: <f43fc5580907120153w2b177418hfa9f4b340d0e0082@mail.gmail.com> (raw)
In-Reply-To: <b2fa41d60907120135ye0f3b0at5b329f03a6bdb336@mail.gmail.com>
On 7/12/09, Igor Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> On Sun, Jul 12, 2009 at 12:09 PM, Blue Swirl<blauwirbel@gmail.com> wrote:
> > On 7/12/09, Igor Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> >> Good trap handling is required to process interrupts.
> >> This patch fixes the following:
> >>
> >> - sparc64 has no wim register
> >> - sparc64 has no psret register, use IE bit of pstate
> >> extract IE checking code to cpu_interrupts_enabled
> >> - alternate globals are not available if cpu has GL feature
> >> in this case bit AG of pstate is constant zero
> >> - write to pstate must actually write pstate
> >> even if cpu has GL feature
> >>
> >> Also timer interrupt is handled using do_interrupt.
> >
> > A bit too much for one patch. Please also remove the code instead of
> > commenting out.
>
>
> I now excluded timer interrupt related part.
> To my mind other changes are essentially tied together.
>
>
> > PUT_PSR for Sparc64 needs CC_OP = CC_OP_FLAGS; like Sparc32.
>
>
> Fixed, please find attached the updated version.
Thanks, applied.
prev parent reply other threads:[~2009-07-12 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 23:03 [Qemu-devel] [PATCH] sparc64: trap handling corrections Igor Kovalenko
2009-07-12 8:09 ` Blue Swirl
2009-07-12 8:35 ` Igor Kovalenko
2009-07-12 8:53 ` 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=f43fc5580907120153w2b177418hfa9f4b340d0e0082@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=igor.v.kovalenko@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).