From: Aurelien Jarno <aurelien@aurel32.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] lsi53c895a: fix Phase Mismatch Jump
Date: Tue, 29 Jun 2010 23:11:50 +0200 [thread overview]
Message-ID: <20100629211150.GA3811@ohm.aurel32.net> (raw)
In-Reply-To: <1276535514-19724-1-git-send-email-pbonzini@redhat.com>
On Mon, Jun 14, 2010 at 07:11:54PM +0200, Paolo Bonzini wrote:
> lsi_bad_phase has a bug in the choice of pmjad1/pmjad2. This does
> not matter with Linux guests because it uses just one routine for
> both, but it breaks Windows 64-bit guests. This is the text
> from the spec:
>
> "[The PMJCTL] bit controls which decision mechanism is used
> when jumping on phase mismatch. When this bit is cleared the
> LSI53C895A will use Phase Mismatch Jump Address 1 (PMJAD1) when
> the WSR bit is cleared and Phase Mismatch Jump Address 2 (PMJAD2)
> when the WSR bit is set. When this bit is set the LSI53C895A will
> use jump address one (PMJAD1) on data out (data out, command,
> message out) transfers and jump address two (PMJAD2) on data in
> (data in, status, message in) transfers."
>
> Which means:
>
> CCNTL0.PMJCTL
> 0 SCNTL2.WSR = 0 PMJAD1
> 0 SCNTL2.WSR = 1 PMJAD2
> 1 out PMJAD1
> 1 in PMJAD2
>
> In qemu, what you get instead is:
>
> CCNTL0.PMJCTL
> 0 out PMJAD1
> 0 in PMJAD2 <<<<<
> 1 out PMJAD1
> 1 in PMJAD1 <<<<<
>
> Considering that qemu always has SCNTL2.WSR cleared, the two marked cases
> (corresponding to phase mismatch on input) are always jumping to the
> wrong PMJAD register. The patch implements the correct semantics.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> > Looks correct. But why not assigning s->pmjad[12] directly? Would
> > improve readability IMO.
>
> No particular reason, hence fine by me.
Thanks, applied.
> hw/lsi53c895a.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/lsi53c895a.c b/hw/lsi53c895a.c
> index f5a91ba..9a37fed 100644
> --- a/hw/lsi53c895a.c
> +++ b/hw/lsi53c895a.c
> @@ -490,10 +490,10 @@ static void lsi_bad_phase(LSIState *s, int out, int new_phase)
> {
> /* Trigger a phase mismatch. */
> if (s->ccntl0 & LSI_CCNTL0_ENPMJ) {
> - if ((s->ccntl0 & LSI_CCNTL0_PMJCTL) || out) {
> - s->dsp = s->pmjad1;
> + if ((s->ccntl0 & LSI_CCNTL0_PMJCTL)) {
> + s->dsp = out ? s->pmjad1 : s->pmjad2;
> } else {
> - s->dsp = s->pmjad2;
> + s->dsp = (s->scntl2 & LSI_SCNTL2_WSR ? s->pmjad2 : s->pmjad1);
> }
> DPRINTF("Data phase mismatch jump to %08x\n", s->dsp);
> } else {
> --
> 1.7.0.1
>
>
>
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-06-29 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 16:41 [Qemu-devel] [PATCH] lsi53c895a: fix Phase Mismatch Jump Paolo Bonzini
2010-06-14 17:05 ` [Qemu-devel] " Jan Kiszka
2010-06-14 17:10 ` Michal Novotny
2010-06-14 17:11 ` [Qemu-devel] [PATCH v2] " Paolo Bonzini
2010-06-25 8:02 ` [Qemu-devel] " Paolo Bonzini
2010-06-29 21:11 ` Aurelien Jarno [this message]
2010-06-14 17:14 ` [Qemu-devel] Re: [PATCH] " Michal Novotny
2010-06-14 17:31 ` Jan Kiszka
2010-06-14 17:34 ` Michal Novotny
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=20100629211150.GA3811@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=pbonzini@redhat.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).