From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Paul Martin <paul.martin@codethink.co.uk>,
Ezequiel Garcia <ezequiel.garcia@imgtec.com>,
Markos Chandras <Markos.Chandras@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH v2] MIPS: Fix a preemption issue with thread's FPU defaults
Date: Tue, 12 May 2015 23:14:43 +0200 [thread overview]
Message-ID: <20150512211443.GA21142@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.11.1505121432540.1538@eddie.linux-mips.org>
On Tue, May 12, 2015 at 03:20:57PM +0100, Maciej W. Rozycki wrote:
On systems with multiple types of FPUs this would also result in a
more consistent behaviour when a process is scheduled between different
CPUs.
Ralf
next prev parent reply other threads:[~2015-05-12 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 14:20 [PATCH v2] MIPS: Fix a preemption issue with thread's FPU defaults Maciej W. Rozycki
2015-05-12 17:28 ` Ezequiel Garcia
2015-05-12 17:28 ` Ezequiel Garcia
2015-05-12 17:34 ` Paul Martin
2015-05-12 21:14 ` Ralf Baechle [this message]
2015-05-12 22:35 ` Maciej W. Rozycki
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=20150512211443.GA21142@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Markos.Chandras@imgtec.com \
--cc=ezequiel.garcia@imgtec.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=paul.martin@codethink.co.uk \
/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.