From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: "Kevin D. Kissell" <kevink@paralogos.com>
Cc: David Daney <david.daney@cavium.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: SMTC: Correct saving of CP0_STATUS
Date: Tue, 30 Aug 2011 13:16:03 +0200 [thread overview]
Message-ID: <20110830111603.GB14243@edde.se.axis.com> (raw)
In-Reply-To: <4E5C3060.70302@paralogos.com>
On Mon, Aug 29, 2011 at 05:35:44PM -0700, Kevin D. Kissell wrote:
> On 08/29/11 17:14, David Daney wrote:
> > On 08/29/2011 04:55 PM, Kevin D. Kissell wrote:
> >> I submitted that exact patch (David's more minimal version) in December
> >> 2010 (and I did test it). Did it not take?
> >
> > Evidently not. Perhaps Ralf will see fit to commit it this time.
>
> Looking back over the exchange and thinking about the date,
> in all fairness to Ralf, when I submitted it, it was a diff -u and
> not a git diff, because I was at my brother-in-law's house for
> the holidays and had no access to my MIPS Linux git machine.
> It got picked up by patchwork.linux-mips.org ( patch/1896 ),
> but was only actually tested by Anoop a couple of days
> later. He confirmed that it solved the problem, but also that
> there were other problems with SMTC in the then-current
> head, apparently relating to timekeeping_notify(). Those
> problems weren't resolved in the context of that email thread,
> so the patch - something along the lines of which really and
> truly is necessary - may have been ignored as a partial fix,
> even though it is a self-contained solution to a self-contained bug.
Interesting. Coincidentally, after getting pass the CP0_Status issue, I ran
into some issues related to time-keeping, but I got the impression I was
seeing a mix of problems with QEMU and possibly the kernel. I never hunted
these issues down though. Maybe I'll give it a go some other time..
It makes me wonder, what is the state of SMTC kernels? Are they widely
used and considered stable?
Or is the SMP mode (1 TC per VPE) the common choice?
Cheers
next prev parent reply other threads:[~2011-08-30 11:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 23:20 [PATCH] MIPS: SMTC: Correct saving of CP0_STATUS Edgar E. Iglesias
2011-08-29 23:45 ` David Daney
2011-08-29 23:45 ` David Daney
2011-08-29 23:53 ` David Daney
2011-08-29 23:55 ` Kevin D. Kissell
2011-08-30 0:14 ` David Daney
2011-08-30 0:35 ` Kevin D. Kissell
2011-08-30 11:16 ` Edgar E. Iglesias [this message]
2011-08-30 16:54 ` Kevin D. Kissell
2011-09-14 15:12 ` Ralf Baechle
2011-09-14 18:20 ` Kevin D. Kissell
2011-08-30 5:57 ` Edgar E. Iglesias
2011-09-15 16:00 ` Ralf Baechle
2011-09-17 1:23 ` Edgar E. Iglesias
2011-09-17 2:00 ` Ralf Baechle
2011-09-17 2:08 ` Edgar E. Iglesias
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=20110830111603.GB14243@edde.se.axis.com \
--to=edgar.iglesias@gmail.com \
--cc=david.daney@cavium.com \
--cc=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.