From: Juergen Gross <jgross@suse.com>
To: Julien Grall <julien@xen.org>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] xen: make include/xen/unaligned.h usable on all architectures
Date: Tue, 5 Dec 2023 13:39:24 +0100 [thread overview]
Message-ID: <e8df45d3-1d7d-432b-b0ca-7532d4b35eae@suse.com> (raw)
In-Reply-To: <1984c65c-72d8-4850-9886-f2b0766224a5@xen.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1225 bytes --]
On 05.12.23 12:53, Julien Grall wrote:
> Hi Juergen,
>
> On 05/12/2023 10:07, Juergen Gross wrote:
>> Instead of defining get_unaligned() and put_unaligned() in a way that
>> is only supporting architectures allowing unaligned accesses, use the
>> same approach as the Linux kernel and let the compiler do the
>> decision how to generate the code for probably unaligned data accesses.
>>
>> Update include/xen/unaligned.h from include/asm-generic/unaligned.h of
>> the Linux kernel.
>>
>> The generated code has been checked to be the same on x86.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Origin: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> 803f4e1eab7a
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>
> Can you outline your end goal? At least on arm32, I believe this will result to
> abort because event if the architecture support unaligned access, we are
> preventing them on Arm32.
I need something like that in Xen tools for supporting packed data accesses
on the 9pfs ring page, so I looked into the hypervisor for related support.
I guess for arm32 using -mno-unaligned-access when building should avoid any
unaligned accesses?
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-12-05 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 10:07 [PATCH 0/2] xen: have a more generic unaligned.h header Juergen Gross
2023-12-05 10:07 ` [PATCH 1/2] xen: make include/xen/unaligned.h usable on all architectures Juergen Gross
2023-12-05 11:53 ` Julien Grall
2023-12-05 12:39 ` Juergen Gross [this message]
2023-12-05 13:31 ` Julien Grall
2023-12-05 13:41 ` Juergen Gross
2023-12-05 13:46 ` Julien Grall
2023-12-05 13:59 ` Jan Beulich
2023-12-05 14:01 ` Julien Grall
2023-12-05 14:10 ` Arnd Bergmann
2023-12-05 14:19 ` Julien Grall
2023-12-05 14:37 ` Arnd Bergmann
2023-12-05 16:29 ` Julien Grall
2023-12-05 16:31 ` Juergen Gross
2023-12-05 14:11 ` Jan Beulich
2023-12-05 14:16 ` Juergen Gross
2023-12-05 13:55 ` Jan Beulich
2023-12-05 14:11 ` Juergen Gross
2023-12-05 10:07 ` [PATCH 2/2] xen: remove asm/unaligned.h Juergen Gross
2023-12-05 13:57 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 16:27 [PATCH 0/2] xen: have a more generic unaligned.h header (take 2) Juergen Gross
2023-12-12 16:27 ` [PATCH 1/2] xen: make include/xen/unaligned.h usable on all architectures Juergen Gross
2023-12-12 16:47 ` Jan Beulich
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=e8df45d3-1d7d-432b-b0ca-7532d4b35eae@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=arnd@arndb.de \
--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.