From: Blue Swirl <blauwirbel@gmail.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@gmail.com>
Subject: [Qemu-devel] Re: [PATCH] sparc32 protect read-only bits in DMA CSR registers
Date: Sat, 22 May 2010 09:22:39 +0000 [thread overview]
Message-ID: <AANLkTinrp6izubeh_E_lSQ6YOWftna5DManWnPPsLFXe@mail.gmail.com> (raw)
In-Reply-To: <1274517536-20889-1-git-send-email-atar4qemu@gmail.com>
Thanks, applied. You forgot SoB-line, I copied it from the previous version.
On Sat, May 22, 2010 at 8:38 AM, Artyom Tarasenko
<atar4qemu@googlemail.com> wrote:
> On a real hardware changing read-only bits has no effect
> Use a mask common for SCSI and Ethernet registers. The crucial
> bit is DMA_INTR, because setting or clearing it may produce
> spurious interrupts.
>
> This patch allows booting Solaris 2.3
> ---
> hw/sparc32_dma.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/hw/sparc32_dma.c b/hw/sparc32_dma.c
> index 3ceb851..b521707 100644
> --- a/hw/sparc32_dma.c
> +++ b/hw/sparc32_dma.c
> @@ -62,6 +62,9 @@
> #define DMA_DRAIN_FIFO 0x40
> #define DMA_RESET 0x80
>
> +/* XXX SCSI and ethernet should have different read-only bit masks */
> +#define DMA_CSR_RO_MASK 0xfe000007
> +
> typedef struct DMAState DMAState;
>
> struct DMAState {
> @@ -187,7 +190,7 @@ static void dma_mem_writel(void *opaque, target_phys_addr_t addr, uint32_t val)
> switch (saddr) {
> case 0:
> if (val & DMA_INTREN) {
> - if (val & DMA_INTR) {
> + if (s->dmaregs[0] & DMA_INTR) {
> DPRINTF("Raise IRQ\n");
> qemu_irq_raise(s->irq);
> }
> @@ -204,16 +207,17 @@ static void dma_mem_writel(void *opaque, target_phys_addr_t addr, uint32_t val)
> val &= ~DMA_DRAIN_FIFO;
> } else if (val == 0)
> val = DMA_DRAIN_FIFO;
> - val &= 0x0fffffff;
> + val &= ~DMA_CSR_RO_MASK;
> val |= DMA_VER;
> + s->dmaregs[0] = (s->dmaregs[0] & DMA_CSR_RO_MASK) | val;
> break;
> case 1:
> s->dmaregs[0] |= DMA_LOADED;
> - break;
> + /* fall through */
> default:
> + s->dmaregs[saddr] = val;
> break;
> }
> - s->dmaregs[saddr] = val;
> }
>
> static CPUReadMemoryFunc * const dma_mem_read[3] = {
> --
> 1.6.2.5
>
>
next prev parent reply other threads:[~2010-05-22 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 8:38 [Qemu-devel] [PATCH] sparc32 protect read-only bits in DMA CSR registers Artyom Tarasenko
2010-05-22 9:22 ` Blue Swirl [this message]
2010-05-22 9:29 ` [Qemu-devel] " Artyom Tarasenko
2010-05-22 9:33 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 21:53 [Qemu-devel] " Artyom Tarasenko
2010-05-22 7:26 ` [Qemu-devel] " Blue Swirl
2010-05-22 8:32 ` Artyom Tarasenko
2010-05-22 9:26 ` Blue Swirl
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=AANLkTinrp6izubeh_E_lSQ6YOWftna5DManWnPPsLFXe@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=atar4qemu@gmail.com \
--cc=atar4qemu@googlemail.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).