From: Oleksii <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Alistair Francis <alistair.francis@wdc.com>,
Bob Eshleman <bobbyeshleman@gmail.com>,
Connor Davis <connojdavis@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 12/23] xen/riscv: introduce io.h
Date: Thu, 07 Mar 2024 21:54:02 +0100 [thread overview]
Message-ID: <d3eabf773211defb2f8a9a22545fca5c7cf3eca1.camel@gmail.com> (raw)
In-Reply-To: <9ec718f3bba178d437035add3c7467011fc3ffc0.camel@gmail.com>
On Thu, 2024-03-07 at 21:49 +0100, Oleksii wrote:
> On Thu, 2024-03-07 at 18:14 +0100, Jan Beulich wrote:
> > For plain writes it should at least be "=Qo" then, yes.
> Constraints Q is a machine specific constraint, and I am not sure
> that
> it makes sense to use "=o" only and probably it is a reason why it is
> enough only "r". Does it make sense?
Probably for RISC-V can be used:
RISC-V—config/riscv/constraints.md
...
A
An address that is held in a general-purpose register.
...
AArch64 family—config/aarch64/constraints.md:
...
Q
A memory address which uses a single base register with no
offset
...
Also 'no offset' explains why it was added 'o' constraint for Arm
additionally.
~ Oleksii
>
> > To me making those
> > input operands on Arm can't have been quite right.
> I don't understand why they both are input, logically it looks like
> an
> address should be an output.
>
> ~ Oleksii
>
next prev parent reply other threads:[~2024-03-07 20:54 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 17:38 [PATCH v5 00/23] [PATCH v4 00/30] Enable build of full Xen for RISC-V Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 01/23] xen/riscv: disable unnecessary configs Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 02/23] xen/riscv: use some asm-generic headers Oleksii Kurochko
2024-02-27 7:35 ` Jan Beulich
2024-02-26 17:38 ` [PATCH v5 03/23] xen/riscv: introduce nospec.h Oleksii Kurochko
2024-02-27 7:38 ` Jan Beulich
2024-02-28 9:59 ` Oleksii
2024-02-29 13:49 ` Julien Grall
2024-02-29 14:01 ` Jan Beulich
2024-02-29 16:09 ` Oleksii
2024-02-29 16:27 ` Jan Beulich
2024-02-26 17:38 ` [PATCH v5 04/23] xen/asm-generic: introduce generic fls() and flsl() functions Oleksii Kurochko
2024-02-29 13:54 ` Julien Grall
2024-02-29 14:03 ` Jan Beulich
2024-02-29 14:08 ` Julien Grall
2024-02-29 16:17 ` Oleksii
2024-02-29 15:52 ` Jan Beulich
2024-02-29 16:25 ` Andrew Cooper
2024-03-01 9:15 ` Oleksii
2024-02-26 17:38 ` [PATCH v5 05/23] xen/asm-generic: introduce generic find first set bit functions Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 06/23] xen/asm-generic: introduce generic ffz() Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 07/23] xen/asm-generic: introduce generic hweight64() Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 08/23] xen/asm-generic: introduce generic non-atomic test_*bit() Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 09/23] xen/riscv: introduce bitops.h Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 10/23] xen/riscv: introduces acrquire, release and full barriers Oleksii Kurochko
2024-03-05 7:42 ` Jan Beulich
2024-02-26 17:38 ` [PATCH v5 11/23] xen/riscv: introduce cmpxchg.h Oleksii Kurochko
2024-03-06 14:56 ` Jan Beulich
2024-03-07 10:35 ` Oleksii
2024-03-07 10:46 ` Jan Beulich
2024-03-07 11:01 ` Oleksii
2024-03-07 11:11 ` Jan Beulich
2024-03-07 12:28 ` Oleksii
2024-02-26 17:38 ` [PATCH v5 12/23] xen/riscv: introduce io.h Oleksii Kurochko
2024-03-06 14:13 ` Jan Beulich
2024-03-07 13:01 ` Oleksii
2024-03-07 13:24 ` Jan Beulich
2024-03-07 13:44 ` Oleksii
2024-03-07 15:32 ` Jan Beulich
2024-03-07 16:21 ` Oleksii
2024-03-07 17:14 ` Jan Beulich
2024-03-07 20:49 ` Oleksii
2024-03-07 20:54 ` Oleksii [this message]
2024-03-08 7:26 ` Jan Beulich
2024-03-08 10:14 ` Oleksii
2024-03-08 11:49 ` Jan Beulich
2024-03-08 11:52 ` Jan Beulich
2024-03-08 12:17 ` Oleksii
2024-03-08 12:54 ` Jan Beulich
2024-03-08 7:18 ` Jan Beulich
2024-02-26 17:38 ` [PATCH v5 13/23] xen/riscv: introduce atomic.h Oleksii Kurochko
2024-03-06 15:31 ` Jan Beulich
2024-03-07 13:30 ` Oleksii
2024-03-07 15:40 ` Jan Beulich
2024-02-26 17:38 ` [PATCH v5 14/23] xen/riscv: introduce monitor.h Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 15/23] xen/riscv: add definition of __read_mostly Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 16/23] xen/riscv: add required things to current.h Oleksii Kurochko
2024-02-26 17:38 ` [PATCH v5 17/23] xen/riscv: add minimal stuff to page.h to build full Xen Oleksii Kurochko
2024-02-26 17:39 ` [PATCH v5 18/23] xen/riscv: add minimal stuff to processor.h " Oleksii Kurochko
2024-03-05 8:05 ` Jan Beulich
2024-03-05 17:34 ` Oleksii
2024-02-26 17:39 ` [PATCH v5 19/23] xen/riscv: add minimal stuff to mm.h " Oleksii Kurochko
2024-03-05 8:17 ` Jan Beulich
2024-03-05 16:46 ` Oleksii
2024-02-26 17:39 ` [PATCH v5 20/23] xen/riscv: introduce vm_event_*() functions Oleksii Kurochko
2024-02-26 17:39 ` [PATCH v5 21/23] xen/rirscv: add minimal amount of stubs to build full Xen Oleksii Kurochko
2024-03-05 8:40 ` Jan Beulich
2024-02-26 17:39 ` [PATCH v5 22/23] xen/riscv: enable full Xen build Oleksii Kurochko
2024-02-26 17:39 ` [PATCH v5 23/23] xen/README: add compiler and binutils versions for RISC-V64 Oleksii Kurochko
2024-02-27 7:55 ` Jan Beulich
2024-02-28 17:03 ` Oleksii
2024-02-28 22:58 ` Julien Grall
2024-02-28 23:11 ` Andrew Cooper
2024-02-29 17:00 ` Oleksii
2024-02-29 7:58 ` Jan Beulich
2024-02-29 10:23 ` Julien Grall
2024-02-29 11:56 ` Jan Beulich
2024-02-29 11:59 ` Jan Beulich
2024-02-29 12:05 ` Andrew Cooper
2024-02-29 12:17 ` Jan Beulich
2024-02-29 12:32 ` Julien Grall
2024-02-29 12:51 ` Jan Beulich
2024-02-29 13:44 ` Julien Grall
2024-02-29 14:07 ` Jan Beulich
2024-02-29 14:14 ` Julien Grall
2024-02-29 17:43 ` Stefano Stabellini
2024-02-29 12:27 ` Julien Grall
2024-02-29 16:54 ` Oleksii
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=d3eabf773211defb2f8a9a22545fca5c7cf3eca1.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=bobbyeshleman@gmail.com \
--cc=connojdavis@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.