From: Blue Swirl <blauwirbel@gmail.com>
To: "Igor V. Kovalenko" <igor.v.kovalenko@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/9] sparc64: interrupts and tick timers v1
Date: Fri, 8 Jan 2010 18:16:25 +0000 [thread overview]
Message-ID: <f43fc5581001081016p5034ab87k4d11d77fd044ca85@mail.gmail.com> (raw)
In-Reply-To: <20100107201810.16653.85771.stgit@skyserv>
Thanks, applied all except 9/9.
On Thu, Jan 7, 2010 at 8:27 PM, Igor V. Kovalenko
<igor.v.kovalenko@gmail.com> wrote:
> The following series is a cleanup over previous one.
>
> v0 -> v1: post-review changes
> - dropped patch "clear exception_index with -1 val" (applied)
> - new patch "change_pstate should have 32bit argument"
> - cleanups for coding style and hexadecimal output convention
> - wrpil is no-op for CONFIG_USER_ONLY
> - restored PIL 15 as non-maskable interrupt level on sparcv8
> - check for PSTATE.IE is replaced with call to cpu_interrupts_enabled()
> - in patch "sparc64: interrupt trap handling"
> cleaned up change in cpu_exec; since sparc64 does not use
> CPU_INTERRUPT_TIMER now, corresponding code branch is unchanged
>
> ---
>
> Igor V. Kovalenko (9):
> sparc64: change_pstate should have 32bit argument
> sparc64: trace pstate and global register set changes
> sparc64: add PIL to cpu state dump
> sparc64: use helper_wrpil to check pending irq on write
> sparc64: check for pending irq when pil, pstate or softint is changed
> sparc64: add macros to deal with softint and timer interrupt
> sparc64: move cpu_interrupts_enabled to cpu.h
> sparc64: interrupt trap handling
> sparc64: reimplement tick timers
>
>
> cpu-exec.c | 28 +++---
> hw/sun4u.c | 225 +++++++++++++++++++++++++++++++++++++---------
> target-sparc/cpu.h | 27 ++++++
> target-sparc/exec.h | 13 ---
> target-sparc/helper.c | 1
> target-sparc/helper.h | 1
> target-sparc/op_helper.c | 81 +++++++++++++++--
> target-sparc/translate.c | 5 -
> 8 files changed, 300 insertions(+), 81 deletions(-)
>
> --
> Kind regards,
> Igor V. Kovalenko
>
>
>
prev parent reply other threads:[~2010-01-08 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 20:27 [Qemu-devel] [PATCH 0/9] sparc64: interrupts and tick timers v1 Igor V. Kovalenko
2010-01-07 20:27 ` [Qemu-devel] [PATCH 1/9] sparc64: change_pstate should have 32bit argument Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 2/9] sparc64: trace pstate and global register set changes Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 3/9] sparc64: add PIL to cpu state dump Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 4/9] sparc64: use helper_wrpil to check pending irq on write Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 5/9] sparc64: check for pending irq when pil, pstate or softint is changed Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 6/9] sparc64: add macros to deal with softint and timer interrupt Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 7/9] sparc64: move cpu_interrupts_enabled to cpu.h Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 8/9] sparc64: interrupt trap handling Igor V. Kovalenko
2010-01-07 20:28 ` [Qemu-devel] [PATCH 9/9] sparc64: reimplement tick timers Igor V. Kovalenko
2010-01-08 18:16 ` 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=f43fc5581001081016p5034ab87k4d11d77fd044ca85@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).