All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args
Date: Fri, 22 May 2020 18:29:08 +0000	[thread overview]
Message-ID: <03a9c1ef-ad74-a1d8-3238-1335c74e141a@ilande.co.uk> (raw)
In-Reply-To: <20200512171527.570109-1-christian.brauner@ubuntu.com>

On 22/05/2020 01:05, Al Viro wrote:

> On Thu, May 21, 2020 at 09:23:50PM +0100, Al Viro wrote:
>> On Thu, May 21, 2020 at 08:42:34PM +0100, Mark Cave-Ayland wrote:
>>
>>>> Can you tell me a bit more about the host in terms of CPU and disk to help figure out
>>>> what's going on?
>>
>> phenom II X6 1100T (6-way 3.3GHz), 8Gb RAM (4Gb given to guest), WDC WD10EACS-00D
>> disk (hdparm -tT gives
>>  Timing cached reads:   6988 MB in  2.00 seconds = 3494.96 MB/sec
>>  Timing buffered disk reads: 280 MB in  3.02 seconds =  92.75 MB/sec
>> )
>>
>>> One other thought I had is that somehow the IVEC IRQs are managing to be overwritten
>>> on a faster host before being read by the guest. Does the following patch display the
>>> FATAL message at the point where things hang?
>>
>>> diff --git a/hw/pci-host/sabre.c b/hw/pci-host/sabre.c
>>> index fae20ee97c..618ebd1300 100644
>>> --- a/hw/pci-host/sabre.c
>>> +++ b/hw/pci-host/sabre.c
>>> @@ -63,6 +63,9 @@
>>>  static inline void sabre_set_request(SabreState *s, unsigned int irq_num)
>>>  {
>>>      trace_sabre_set_request(irq_num);
>>> +    if (s->irq_request != 0 && s->irq_request != NO_IRQ_REQUEST) {
>>> +        fprintf(stderr, "FATAL: still waiting for IRQ %x, now %x\n", s->irq_request,
>>> irq_num);
>>> +    }
>>>      s->irq_request = irq_num;
>>>      qemu_set_irq(s->ivec_irqs[irq_num], 1);
>>>  }
>>
>> I have to go AFK right now, will test when I get back (should be about an
>> hour or two)
> 
> Hang, nothing on stderr until killed, at which point it gave the expected
> qemu-system-sparc64: terminating on signal 15 from pid 15917 (-bash)
> IOW, stderr got flushed after hang - that fprintf simply has not triggered.

Okay thanks for giving that a go. I have one other possibility that I want to
eliminate: I see that you are using a very up-to-date 5.6.0-1-sparc64, whereas I was
testing with the stock CD image (and indeed, an older revision than the one that is
currently available in Debian ports).

When you have a moment, can you grab the latest qemu from git master since it has
some fixes for -kernel/-initrd, and then try booting your same sparc64 disk image but
 passing in explicit -kernel and -initrd parameters pointing to the same ones that I
am using. I'll send you a download link off-list.


ATB,

Mark.

      parent reply	other threads:[~2020-05-22 18:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 17:15 [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args Christian Brauner
2020-05-12 17:15 ` Christian Brauner
2020-05-12 17:15 ` [PATCH 1/3] sparc64: enable HAVE_COPY_THREAD_TLS Christian Brauner
2020-05-12 17:15   ` Christian Brauner
2020-05-12 20:04   ` David Miller
2020-05-12 20:04     ` David Miller
2020-05-12 17:15 ` [PATCH 2/3] sparc: share process creation helpers between sparc and sparc64 Christian Brauner
2020-05-12 17:15   ` Christian Brauner
2020-05-12 17:15 ` [PATCH 3/3] sparc: unconditionally enable HAVE_COPY_THREAD_TLS Christian Brauner
2020-05-12 17:15   ` Christian Brauner
2020-05-12 20:06 ` [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args David Miller
2020-05-12 20:06   ` David Miller
2020-05-17 15:01   ` Christian Brauner
2020-05-17 15:01     ` Christian Brauner
2020-05-17 16:34     ` Mark Cave-Ayland
2020-05-17 16:34       ` Mark Cave-Ayland
2020-05-17 22:13       ` Al Viro
2020-05-17 22:13         ` Al Viro
2020-05-18 18:18         ` Al Viro
2020-05-18 18:18           ` Al Viro
2020-05-18 18:23           ` Christian Brauner
2020-05-18 18:23             ` Christian Brauner
2020-05-18 19:58           ` Mark Cave-Ayland
2020-05-18 19:58             ` Mark Cave-Ayland
2020-05-18 23:08 ` Al Viro
2020-05-19  0:24 ` Al Viro
2020-05-21 19:08 ` Mark Cave-Ayland
2020-05-21 19:42 ` Mark Cave-Ayland
2020-05-21 20:23 ` Al Viro
2020-05-22  0:05 ` Al Viro
2020-05-22 18:29 ` Mark Cave-Ayland [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=03a9c1ef-ad74-a1d8-3238-1335c74e141a@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=sparclinux@vger.kernel.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 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.