All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Parri <parri.andrea@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: paulmck@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, mmaas@google.com,
	hboehm@google.com, striker@us.ibm.com
Subject: Re: [RFC PATCH] membarrier: riscv: Provide core serializing command
Date: Mon, 7 Aug 2023 15:19:18 +0200	[thread overview]
Message-ID: <ZNDvVlbubtOoto0p@andrea> (raw)
In-Reply-To: <e17900b8-ad20-e5c1-2443-0f9559f1fdb8@efficios.com>

> One more noteworthy detail: if a system call similar to ARM cacheflush(2) is implemented for
> RISC-V, perhaps an iovec ABI (similar to readv(2)/writev(2)) would be relevant to handle
> batching of cache flushing when address ranges are not contiguous. Maybe with a new name
> like "cacheflushv(2)", so eventually other architectures could implement it as well ?

I believe that's a sensible idea.  But the RISC-V maintainers can provide
a more reliable feedback.

  Andrea

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Andrea Parri <parri.andrea@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: paulmck@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, mmaas@google.com,
	hboehm@google.com, striker@us.ibm.com
Subject: Re: [RFC PATCH] membarrier: riscv: Provide core serializing command
Date: Mon, 7 Aug 2023 15:19:18 +0200	[thread overview]
Message-ID: <ZNDvVlbubtOoto0p@andrea> (raw)
In-Reply-To: <e17900b8-ad20-e5c1-2443-0f9559f1fdb8@efficios.com>

> One more noteworthy detail: if a system call similar to ARM cacheflush(2) is implemented for
> RISC-V, perhaps an iovec ABI (similar to readv(2)/writev(2)) would be relevant to handle
> batching of cache flushing when address ranges are not contiguous. Maybe with a new name
> like "cacheflushv(2)", so eventually other architectures could implement it as well ?

I believe that's a sensible idea.  But the RISC-V maintainers can provide
a more reliable feedback.

  Andrea

  reply	other threads:[~2023-08-07 13:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  4:01 [RFC PATCH] membarrier: riscv: Provide core serializing command Andrea Parri
2023-08-03  4:01 ` Andrea Parri
2023-08-03 15:45 ` Andrea Parri
2023-08-03 15:45   ` Andrea Parri
2023-08-03 20:28   ` Mathieu Desnoyers
2023-08-03 20:28     ` Mathieu Desnoyers
2023-08-04  0:16     ` Andrea Parri
2023-08-04  0:16       ` Andrea Parri
2023-08-04 14:20       ` Mathieu Desnoyers
2023-08-04 14:20         ` Mathieu Desnoyers
2023-08-04 14:59         ` Andrea Parri
2023-08-04 14:59           ` Andrea Parri
2023-08-04 18:05           ` Mathieu Desnoyers
2023-08-04 18:05             ` Mathieu Desnoyers
2023-08-04 19:16             ` Andrea Parri
2023-08-04 19:16               ` Andrea Parri
2023-08-04 20:06               ` Mathieu Desnoyers
2023-08-04 20:06                 ` Mathieu Desnoyers
2023-08-07 13:19                 ` Andrea Parri [this message]
2023-08-07 13:19                   ` Andrea Parri
2023-10-13 17:29                   ` Palmer Dabbelt
2023-10-13 17:29                     ` Palmer Dabbelt
2023-10-13 18:49                     ` Mathieu Desnoyers
2023-10-13 18:49                       ` Mathieu Desnoyers
2023-10-16 18:27                       ` Robbin Ehn
2023-10-16 18:27                         ` Robbin Ehn
2023-11-09 19:24                       ` Andrea Parri
2023-11-09 19:24                         ` Andrea Parri
2023-11-10  6:33                         ` [PATCH 1/2] locking: Introduce prepare_sync_core_cmd() kernel test robot
2023-11-10  6:33                           ` kernel test robot
2023-11-23  1:07                         ` [RFC PATCH] membarrier: riscv: Provide core serializing command Charlie Jenkins
2023-11-23  1:07                           ` Charlie Jenkins
2023-11-23  2:13                           ` Mathieu Desnoyers
2023-11-23  2:13                             ` Mathieu Desnoyers
2023-11-27 10:44                             ` Andrea Parri
2023-11-27 10:44                               ` Andrea Parri
2023-11-23  6:52                           ` Robbin Ehn
2023-11-23  6:52                             ` Robbin Ehn

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=ZNDvVlbubtOoto0p@andrea \
    --to=parri.andrea@gmail.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=hboehm@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mmaas@google.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulmck@kernel.org \
    --cc=striker@us.ibm.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 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.