public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	"Marco Crivellari" <marco.crivellari@suse.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Frederic Weisbecker" <frederic@kernel.org>,
	"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Huacai Chen" <chenhuacai@kernel.org>
Subject: Re: [PATCH v6 1/1] MIPS: Fix idle VS timer enqueue
Date: Tue, 01 Apr 2025 10:31:17 +0100	[thread overview]
Message-ID: <3f7f6ced-98e8-4101-aa83-3692e14222ca@app.fastmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2503311348560.47733@angie.orcam.me.uk>



在2025年3月31日星期周一 下午9:09,Maciej W. Rozycki写道:
[...]
>
>  FAOD I have one MIPS32r2 system wired for testing, but that might not be 
> the most interesting configuration to verify as it'll now just use EI/EHB 
> to enable interrupts ahead of WAIT.  I could try an R1 kernel instead, but 
> I'm not sure if it can be made to work owing to the differences in the FPU 
> between R1 and R2 for the MIPS32 ISA.  I used to have a MIPS64 (R1) system 
> there, but the CPU daughtercard sadly stopped working 3 years ago and I 
> wasn't able to repair it, owing to the lack of available spare parts (it's 
> most likely a dead CPU).

I can test on legacy (R1 version) 4Kc RTL simulator if you wish. Is there any
thing specific you want to test? I think I can try interrupt flood and see if
there is any deadlock.

The simulation is painfully slow, so I'd wish to minimize test vector.

Thanks


-- 
- Jiaxun

  reply	other threads:[~2025-04-01  9:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 19:40 [PATCH v6 0/1] MIPS: Fix idle VS timer enqueue Marco Crivellari
2025-03-15 19:40 ` [PATCH v6 1/1] " Marco Crivellari
2025-03-19 11:07   ` Thomas Bogendoerfer
2025-03-19 14:06     ` Frederic Weisbecker
2025-03-19 14:42       ` Thomas Bogendoerfer
2025-03-19 15:01         ` Frederic Weisbecker
2025-03-19 14:43     ` Frederic Weisbecker
2025-03-19 15:31       ` Thomas Bogendoerfer
2025-03-20  8:44         ` Marco Crivellari
2025-03-21  9:38           ` Thomas Bogendoerfer
2025-03-21 10:44             ` Marco Crivellari
2025-03-21 11:17               ` Thomas Bogendoerfer
2025-03-21 11:55                 ` Maciej W. Rozycki
2025-03-21 11:53   ` Maciej W. Rozycki
2025-03-21 16:15     ` Marco Crivellari
2025-03-21 20:11       ` Maciej W. Rozycki
2025-03-25 14:08         ` Marco Crivellari
2025-03-26  1:20           ` Huacai Chen
2025-03-26  9:46             ` Marco Crivellari
2025-03-26 11:34               ` Thomas Bogendoerfer
2025-03-26 16:01               ` Maciej W. Rozycki
2025-03-28 10:42           ` Maciej W. Rozycki
2025-03-28 14:18             ` Maciej W. Rozycki
2025-03-31 10:11               ` Marco Crivellari
2025-03-31 20:09                 ` Maciej W. Rozycki
2025-04-01  9:31                   ` Jiaxun Yang [this message]
2025-04-02 11:42                   ` Marco Crivellari
2025-04-03 12:00                     ` Maciej W. Rozycki
2025-04-03 13:01                       ` Marco Crivellari
2025-04-03 20:17                         ` Maciej W. Rozycki
2025-04-04  3:18                           ` Marco Crivellari
2025-03-21 21:09     ` Frederic Weisbecker
2025-03-22 16:08       ` Maciej W. Rozycki
2025-03-25 13:31         ` Frederic Weisbecker

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=3f7f6ced-98e8-4101-aa83-3692e14222ca@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=anna-maria@linutronix.de \
    --cc=chenhuacai@kernel.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=marco.crivellari@suse.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tsbogend@alpha.franken.de \
    /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