From: Stefan Berger <stefanb@linux.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Manolo de Medici <manolodemedici@gmail.com>
Cc: qemu-devel@nongnu.org, bug-hurd@gnu.org
Subject: Re: [PATCH v2 4/4] Exclude TPM ioctls definitions for the GNU/Hurd
Date: Mon, 22 Jan 2024 14:30:20 -0500 [thread overview]
Message-ID: <130d2f10-4165-4d35-ade3-e6080e2a109f@linux.ibm.com> (raw)
In-Reply-To: <CAFEAcA_ZyphRxH59VHEpnS_8D4YuBFSZeODwRbMjrqhkggD-Cw@mail.gmail.com>
On 1/22/24 12:16, Peter Maydell wrote:
> On Thu, 18 Jan 2024 at 16:04, Manolo de Medici <manolodemedici@gmail.com> wrote:
>>
>> The Hurd currently doesn't have any TPM driver, compilation fails
>> for missing symbols unless these are left undefined.
>>
>> Signed-off-by: Manolo de Medici <manolo.demedici@gmail.com>
>> ---
>> backends/tpm/tpm_ioctl.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/backends/tpm/tpm_ioctl.h b/backends/tpm/tpm_ioctl.h
>> index 1933ab6855..c721bf8847 100644
>> --- a/backends/tpm/tpm_ioctl.h
>> +++ b/backends/tpm/tpm_ioctl.h
>> @@ -274,7 +274,7 @@ typedef struct ptm_lockstorage ptm_lockstorage;
>> #define PTM_CAP_SEND_COMMAND_HEADER (1 << 15)
>> #define PTM_CAP_LOCK_STORAGE (1 << 16)
>>
>> -#ifndef _WIN32
>> +#if !defined(_WIN32) && !defined(__GNU__)
>> enum {
>> PTM_GET_CAPABILITY = _IOR('P', 0, ptm_cap),
>> PTM_INIT = _IOWR('P', 1, ptm_init),
>> --
>> 2.43.0
>
> This looks plausible as a change, but looking at the history
> of the file in git it seems like this is a file we import
> from a third-party swtpm project.
>
> Stefan: should we get this change made in the swtpm project
> too? Or have we diverged from that copy of the header?
The diffs are minimal at the moment:
$ diff swtpm/include/swtpm/tpm_ioctl.h qemu/backends/tpm/tpm_ioctl.h
15,16d14
< #include <stdint.h>
< #include <sys/types.h>
Since we already handle _WIN32 we can just take this case for __GNU__.
Stefan
> If the latter, then the simple thing woud be to delete
> this enum entirely, because as far as I can see we don't
> use any of the values in QEMU, so we can avoid the
> portability problem that way.
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2024-01-22 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 16:04 [PATCH v2 4/4] Exclude TPM ioctls definitions for the GNU/Hurd Manolo de Medici
2024-01-22 17:16 ` Peter Maydell
2024-01-22 19:30 ` Stefan Berger [this message]
2024-01-22 20:46 ` Peter Maydell
2024-01-22 21:50 ` Stefan Berger
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=130d2f10-4165-4d35-ade3-e6080e2a109f@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=bug-hurd@gnu.org \
--cc=manolodemedici@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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 NNTP newsgroup(s).