From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Hans de Goede <hdegoede@redhat.com>,
Borislav Petkov <bp@alien8.de>,
"Limonciello, Mario" <mario.limonciello@amd.com>,
linux-edac@vger.kernel.org, markgross@kernel.org,
platform-driver-x86@vger.kernel.org, "Luck,
Tony" <tony.luck@intel.com>
Cc: yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
avadhut.naik@amd.com
Subject: Re: [PATCH 1/2] platform/x86/amd: Introduce AMD Address Translation Library
Date: Wed, 9 Aug 2023 11:05:51 -0400 [thread overview]
Message-ID: <5b3c306a-059d-479f-8ad0-c914de8a2def@amd.com> (raw)
In-Reply-To: <a64fe3ad-cb2a-3816-fefe-700433926492@redhat.com>
On 8/9/2023 10:38 AM, Hans de Goede wrote:
> Hi,
>
> On 8/8/23 16:07, Yazen Ghannam wrote:
>> On 8/8/2023 8:10 AM, Borislav Petkov wrote:
>>> On August 8, 2023 5:17:33 AM GMT+02:00, "Limonciello, Mario" <mario.limonciello@amd.com> wrote:
>>>> Given it's 'library code' to be used by a bunch of things and also want to be able to use a module, what about putting it in lib/? There's plenty of library code there as tristate.
>>>
>>> It is x86-specific so not in there. Also, it might be used by multiple things so you want it as a separate "translation" service which is called by other modules.
>>>
>>
>> There are modules in arch/x86, so I guess that's not an issue (not sure what I was thinking).
>
> Right, I think arch/x86 makes sense.
>
> As for putting this under drivers/platform/x86/amd as initially suggested. That means that any code which wants to select this because it needs the functions also must select X86_PLATFORM_DEVICES, so IMHO it is better to put it in another place.
>
Good point, and thanks for your feedback!
Thanks,
Yazen
next prev parent reply other threads:[~2023-08-09 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 18:55 [PATCH 0/2] AMD Address Translation Library Yazen Ghannam
2023-08-02 18:55 ` [PATCH 1/2] platform/x86/amd: Introduce " Yazen Ghannam
2023-08-07 20:44 ` Yazen Ghannam
2023-08-08 3:17 ` Limonciello, Mario
2023-08-08 12:10 ` Borislav Petkov
2023-08-08 14:07 ` Yazen Ghannam
2023-08-08 14:20 ` Borislav Petkov
2023-08-08 14:28 ` Yazen Ghannam
2023-08-08 14:37 ` Borislav Petkov
2023-08-08 15:18 ` Yazen Ghannam
2023-08-08 15:58 ` Borislav Petkov
2023-08-08 16:24 ` Yazen Ghannam
2023-08-09 14:38 ` Hans de Goede
2023-08-09 15:05 ` Yazen Ghannam [this message]
2023-08-02 18:55 ` [PATCH 2/2] EDAC/amd64: Use new " Yazen Ghannam
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=5b3c306a-059d-479f-8ad0-c914de8a2def@amd.com \
--to=yazen.ghannam@amd.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tony.luck@intel.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.