From: Guenter Roeck <linux@roeck-us.net>
To: Matthew Sakai <msakai@redhat.com>, Kenneth Raeburn <raeburn@redhat.com>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org
Subject: Re: [PATCH v4 02/39] dm vdo: add the MurmurHash3 fast hashing algorithm
Date: Wed, 20 Mar 2024 15:59:35 -0700 [thread overview]
Message-ID: <b61ce2b5-c291-4f99-a459-1f9a056ccca1@roeck-us.net> (raw)
In-Reply-To: <cee6169f-f635-e3fb-29a7-e68829cdf1db@redhat.com>
On 3/20/24 14:44, Matthew Sakai wrote:
>
> On 3/18/24 16:54, Guenter Roeck wrote:
>> On 3/18/24 13:37, Kenneth Raeburn wrote:
>>> (resend because of accidental HTML lossage)
>>>
>>> On Thu, Mar 14, 2024 at 7:38 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>>> On sparc64, with gcc 11.4, the above code results in:
>>>>
>>>> ERROR: modpost: "__bswapdi2" [drivers/md/dm-vdo/dm-vdo.ko] undefined!
>>>>
>>>> Guenter
>>>
>>> Thanks for catching that. I don't think our team has any sparc
>>> machines readily available for testing.
>>> This is an artifact of our having imported user-mode code to use in
>>> the kernel. We should probably be using le64_to_cpup and friends, as
>>> we do elsewhere, so it doesn't try to pull in libgcc support routines.
>>>
>>
>> I am kind of getting wary about reporting such issues. Should I drop
>> building dm-vdo images for sparc ? Would it be possible to add
>> "depends on BROKEN if SPARC" configuration option to indicate that
>> the code isn't expected to be buildable on sparc, much less work ?
>>
>> Thanks,
>> Guenter
>>
>
> Could you try out the patch I just sent to see if it fixes your build problem?
>
Sure, will do.
Guenter
next prev parent reply other threads:[~2024-03-20 23:04 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 21:40 [PATCH v4 00/39] dm vdo: add the dm-vdo deduplication and compression DM target Matthew Sakai
2023-10-26 21:40 ` [PATCH v4 01/39] dm: add documentation for dm-vdo target Matthew Sakai
2023-10-26 21:40 ` [PATCH v4 02/39] dm vdo: add the MurmurHash3 fast hashing algorithm Matthew Sakai
2024-03-14 23:35 ` Guenter Roeck
2024-03-18 20:37 ` Kenneth Raeburn
2024-03-18 20:54 ` Guenter Roeck
2024-03-19 1:14 ` Matthew Sakai
2024-03-20 21:44 ` Matthew Sakai
2024-03-20 22:59 ` Guenter Roeck [this message]
2023-10-26 21:41 ` [PATCH v4 03/39] dm vdo: add memory allocation utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 04/39] dm vdo: add basic logging and support utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 05/39] dm vdo: add vdo type declarations, constants, and simple data structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 06/39] dm vdo: add thread and synchronization utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 07/39] dm vdo: add specialized request queueing functionality Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 08/39] dm vdo: add basic hash map data structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 09/39] dm vdo: add deduplication configuration structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 10/39] dm vdo: add deduplication index storage interface Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 11/39] dm vdo: implement the delta index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 12/39] dm vdo: implement the volume index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 13/39] dm vdo: implement the open chapter and chapter indexes Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 14/39] dm vdo: implement the chapter volume store Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 15/39] dm vdo: implement top-level deduplication index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 16/39] dm vdo: implement external deduplication index interface Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 17/39] dm vdo: add administrative state and action manager Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 18/39] dm vdo: add vio, the request object for vdo metadata Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 19/39] dm vdo: add data_vio, the request object which services incoming bios Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 20/39] dm vdo: add flush support Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 21/39] dm vdo: add the vdo io_submitter Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 22/39] dm vdo: add hash locks and hash zones Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 23/39] dm vdo: add use of deduplication index in " Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 24/39] dm vdo: add the compressed block bin packer Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 25/39] dm vdo: add slab structure, slab journal and reference counters Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 26/39] dm vdo: add the slab summary Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 27/39] dm vdo: add the block allocators and physical zones Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 28/39] dm vdo: add the slab depot Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 29/39] dm vdo: add the block map Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 30/39] dm vdo: implement the block map page cache Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 31/39] dm vdo: add the recovery journal Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 32/39] dm vdo: add repair of damaged vdo volumes Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 33/39] dm vdo: add the primary vdo structure Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 34/39] dm vdo: add the on-disk formats and marshalling of vdo structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 35/39] dm vdo: add statistics reporting Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 36/39] dm vdo: add sysfs support for setting parameters and fetching stats Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 37/39] dm vdo: add debugging support Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 38/39] dm vdo: add the top-level DM target Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 39/39] dm vdo: enable configuration and building of dm-vdo Matthew Sakai
2023-11-01 18:28 ` [PATCH v4 00/39] dm vdo: add the dm-vdo deduplication and compression DM target Mike Snitzer
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=b61ce2b5-c291-4f99-a459-1f9a056ccca1@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=msakai@redhat.com \
--cc=raeburn@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).