From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Paolo Bonzini <pbonzini@redhat.com>, Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 5/8] target-sparc: Use global registers for the register window
Date: Fri, 24 Jun 2016 11:42:21 +0100 [thread overview]
Message-ID: <6c98d3be-ec72-cd33-1e74-fc32dea6a865@ilande.co.uk> (raw)
In-Reply-To: <03d5a05a-2674-b755-49d7-5a46dcadc237@redhat.com>
On 24/06/16 07:36, Paolo Bonzini wrote:
> On 24/06/2016 05:57, Richard Henderson wrote:
>>
>> Whatever happens, it happens after 10GB of logs, which is simply too
>> much to sift through. I've tried to narrow it down, but the lack of a
>> hardware tlb refill means that we get hundreds of thousands of Data
>> Access Faults that are simply TLB misses and not the actual Segmentation
>> Fault in question.
>>
>> It doesn't seem to affect other OSes, so I can't imagine what quirk is
>> being exercised in this case.
>>
>> As loath as I am to suggest it, we may have to revert the sparc indirect
>> register patch for the release.
>
> We have more than a month. If it's reproducible, it can be fixed. :)
>
>> I do now ping the rest of my sparc improvements patchset. It's
>> completely independent of the use of indirect registers.
>
> Mark, perhaps you can try to use migration to reduce the amount of
> logging? (Start QEMU with -snapshot, try to stop the vm before it
> fails. If you succeed, do a "migrate exec:cat>foo.sav" followed by
> "commit"; if you fail, try again).
Yeah, given the improvements that Richard has made, I'd prefer not to
revert if at all possible. Finally I have some spare time today so I'll
try and get this down to an easily-testable qcow2 image that can
reproduce the issue.
ATB,
Mark.
next prev parent reply other threads:[~2016-06-24 10:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 18:33 [Qemu-devel] [PULL 0/8] tcg queued patches Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 1/8] tcg: Work around clang bug wrt enum ranges, part 2 Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 2/8] tcg: Implement indirect memory registers Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 3/8] tcg: Allocate indirect_base temporaries in a different order Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 4/8] target-sparc: Tidy global register initialization Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 5/8] target-sparc: Use global registers for the register window Richard Henderson
2016-06-14 21:52 ` Mark Cave-Ayland
2016-06-16 20:26 ` Richard Henderson
2016-06-16 21:53 ` Mark Cave-Ayland
2016-06-24 3:57 ` Richard Henderson
2016-06-24 6:36 ` Paolo Bonzini
2016-06-24 8:12 ` Peter Maydell
2016-06-24 8:16 ` Paolo Bonzini
2016-06-24 10:42 ` Mark Cave-Ayland [this message]
2016-06-24 12:03 ` Paolo Bonzini
2016-06-24 12:35 ` Artyom Tarasenko
2016-02-23 18:33 ` [Qemu-devel] [PULL 6/8] tcg: Rename tcg-target.c to tcg-target.inc.c Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 7/8] scripts/clean-includes: Ignore .inc.c files Richard Henderson
2016-02-23 18:33 ` [Qemu-devel] [PULL 8/8] tcg: Remove unnecessary osdep.h includes from tcg-target.inc.c Richard Henderson
2016-02-25 9:47 ` [Qemu-devel] [PULL 0/8] tcg queued patches Peter Maydell
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=6c98d3be-ec72-cd33-1e74-fc32dea6a865@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.