From: Conor Dooley <conor@kernel.org>
To: Andy Chiu <andy.chiu@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, greentime.hu@sifive.com,
guoren@linux.alibaba.com, bjorn@kernel.org, peterz@infradead.org,
tglx@linutronix.de, "Albert Ou" <aou@eecs.berkeley.edu>,
"Oleg Nesterov" <oleg@redhat.com>, "Guo Ren" <guoren@kernel.org>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Vincent Chen" <vincent.chen@sifive.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Andrew Bresticker" <abrestic@rivosinc.com>,
"Mathis Salmen" <mathis.salmen@matsal.de>
Subject: Re: [v3, 4/5] riscv: vector: do not pass task_struct into riscv_v_vstate_{save,restore}()
Date: Tue, 24 Oct 2023 12:26:55 +0100 [thread overview]
Message-ID: <20231024-dejected-boundless-d07204fad441@spud> (raw)
In-Reply-To: <20231019154552.23351-5-andy.chiu@sifive.com>
[-- Attachment #1.1: Type: text/plain, Size: 667 bytes --]
On Thu, Oct 19, 2023 at 03:45:51PM +0000, Andy Chiu wrote:
> riscv_v_vstate_{save,restore}() can operate only on the knowlege of
> struct __riscv_v_ext_state, and struct pt_regs. Let the caller decides
> which should be passed into the function. Meanwhile, the kernel-mode
> Vector is going to introduce another vstate, so this also makes functions
> potentially able to be reused.
>
> Signed-off-by: Andy Chiu <andy.chiu@sifive.com>
> ---
> Changelog v3:
> - save V context after get_cpu_vector_context
> Changelog v2:
> - fix build fail that get caught on this patch (Conor)
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-24 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:45 [v3, 0/5] riscv: support kernel-mode Vector Andy Chiu
2023-10-19 15:45 ` [v3, 1/5] riscv: Add support for kernel mode vector Andy Chiu
2023-10-24 11:16 ` Conor Dooley
2023-10-19 15:45 ` [v3, 2/5] riscv: Add vector extension XOR implementation Andy Chiu
2023-10-19 15:45 ` [v3, 3/5] riscv: sched: defer restoring Vector context for user Andy Chiu
2023-10-24 11:24 ` Conor Dooley
2023-10-19 15:45 ` [v3, 4/5] riscv: vector: do not pass task_struct into riscv_v_vstate_{save,restore}() Andy Chiu
2023-10-24 11:26 ` Conor Dooley [this message]
2023-10-19 15:45 ` [v3, 5/5] riscv: vector: allow kernel-mode Vector with preemption Andy Chiu
2023-10-20 7:02 ` Andy Chiu
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=20231024-dejected-boundless-d07204fad441@spud \
--to=conor@kernel.org \
--cc=abrestic@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathis.salmen@matsal.de \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.chen@sifive.com \
/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