Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>, <rusty@rustcorp.com.au>,
	<alexinbeijing@gmail.com>, <paul.burton@imgtec.com>,
	<david.daney@cavium.com>, <alex@alex-smith.me.uk>,
	<linux-kernel@vger.kernel.org>, <james.hogan@imgtec.com>,
	<markos.chandras@imgtec.com>, <macro@linux-mips.org>,
	<eunb.song@samsung.com>, <manuel.lauss@gmail.com>,
	<andreas.herrmann@caviumnetworks.com>
Subject: Re: [PATCH 1/2] MIPS: MSA: bugfix - disable MSA during thread switch correctly
Date: Fri, 22 May 2015 12:06:08 -0700	[thread overview]
Message-ID: <555F7E20.3040903@imgtec.com> (raw)
In-Reply-To: <555F776E.3070904@imgtec.com>

Ralf,

If there was TIF_USEDMSA in "prev" task then it means that all MSA HW is 
in use.
And switch_to() checks this and transfers it to resume() to indicate 
that MSA processing should be done.

Macro call "msa_save_all    a0" right before disabling MSA in Config5 
does a save of MSA registers. If it doesn't cause an exception then it 
means that Config5 does exist and Config5.MIPS_CONF5_MSAEN does exist too.

- Leonid.

WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, rusty@rustcorp.com.au,
	alexinbeijing@gmail.com, paul.burton@imgtec.com,
	david.daney@cavium.com, alex@alex-smith.me.uk,
	linux-kernel@vger.kernel.org, james.hogan@imgtec.com,
	markos.chandras@imgtec.com, macro@linux-mips.org,
	eunb.song@samsung.com, manuel.lauss@gmail.com,
	andreas.herrmann@caviumnetworks.com
Subject: Re: [PATCH 1/2] MIPS: MSA: bugfix - disable MSA during thread switch correctly
Date: Fri, 22 May 2015 12:06:08 -0700	[thread overview]
Message-ID: <555F7E20.3040903@imgtec.com> (raw)
Message-ID: <20150522190608.B-cf2VGNNXGf--mo6vHIrnJkzR1cvkIprrxdJs129os@z> (raw)
In-Reply-To: <555F776E.3070904@imgtec.com>

Ralf,

If there was TIF_USEDMSA in "prev" task then it means that all MSA HW is 
in use.
And switch_to() checks this and transfers it to resume() to indicate 
that MSA processing should be done.

Macro call "msa_save_all    a0" right before disabling MSA in Config5 
does a save of MSA registers. If it doesn't cause an exception then it 
means that Config5 does exist and Config5.MIPS_CONF5_MSAEN does exist too.

- Leonid.

  parent reply	other threads:[~2015-05-22 19:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:13 [PATCH 0/2] MIPS: MSA: bugfixes of context switch Leonid Yegoshin
2015-05-19 21:13 ` Leonid Yegoshin
2015-05-19 21:13 ` [PATCH 1/2] MIPS: MSA: bugfix - disable MSA during thread switch correctly Leonid Yegoshin
2015-05-19 21:13   ` Leonid Yegoshin
2015-05-21  9:12   ` Paul Burton
2015-05-21  9:12     ` Paul Burton
2015-05-21 16:11     ` Leonid Yegoshin
2015-05-21 16:11       ` Leonid Yegoshin
2015-05-21 16:20   ` [PATCH] MIPS: tidy up FPU context switching Paul Burton
2015-05-21 16:20     ` Paul Burton
2015-05-22 10:42     ` [PATCH v2] " Paul Burton
2015-05-22 10:42       ` Paul Burton
2015-05-22  9:38   ` [PATCH 1/2] MIPS: MSA: bugfix - disable MSA during thread switch correctly Ralf Baechle
2015-05-22 18:37     ` Leonid Yegoshin
2015-05-22 18:37       ` Leonid Yegoshin
2015-05-22 19:06       ` Leonid Yegoshin [this message]
2015-05-22 19:06         ` Leonid Yegoshin
2015-05-22 23:20       ` Ralf Baechle
2015-05-23  0:00         ` Leonid Yegoshin
2015-05-23  0:00           ` Leonid Yegoshin
2015-05-19 21:13 ` [PATCH 2/2] MIPS: MSA: bugfix of keeping MSA live context through clone or fork Leonid Yegoshin
2015-05-19 21:13   ` Leonid Yegoshin
2015-05-20 19:23   ` Leonid Yegoshin
2015-05-20 19:23     ` Leonid Yegoshin

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=555F7E20.3040903@imgtec.com \
    --to=leonid.yegoshin@imgtec.com \
    --cc=alex@alex-smith.me.uk \
    --cc=alexinbeijing@gmail.com \
    --cc=andreas.herrmann@caviumnetworks.com \
    --cc=david.daney@cavium.com \
    --cc=eunb.song@samsung.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    --cc=markos.chandras@imgtec.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=rusty@rustcorp.com.au \
    /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