From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: "Phil Dennis-Jordan" <phil@philjordan.eu>,
"Pedro Tôrres" <t0rr3sp3dr0@gmail.com>,
rene@exactcode.de, "Kiszka, Jan" <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Graf, Alexander" <agraf@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
suse@csgraf.de, afaerber <afaerber@suse.de>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] hw/misc: applesmc: use host osk as default on macs
Date: Mon, 11 Oct 2021 10:36:08 -0400 [thread overview]
Message-ID: <YWRL2DmlJK3yjV8c@errol.ini.cmu.edu> (raw)
In-Reply-To: <d5ab8786-bec9-b551-bf22-ef1bdace3f2b@eik.bme.hu>
On Mon, 11 Oct 2021 15:40:07 +0200, balaton@eik.bme.hu wrote:
> I guess a frequent use case for running macOS guests with keys from host
> would be on hosts running macOS too so a solution that works both on macOS
> and Linux might be better than a Linux specific one which then needs
> another way to do the same on macOS. Looks like there's free code for that
> too and you don't have to convince a maintainer either.
I mostly agree with you (hadn't given much thought to qemu on macOSX),
with the small caveat that (on Linux) you'll end up racing the kernel
applesmc driver for access to the physical hardware; not sure whether
you'd run into anything similar on host-side macOSX as well, never
actually used it much as a developer... :)
Cheers,
--Gabriel
next prev parent reply other threads:[~2021-10-11 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 20:24 [PATCH] hw/misc: applesmc: use host osk as default on macs Pedro Tôrres
2021-10-04 8:37 ` Paolo Bonzini
2021-10-08 12:03 ` Phil Dennis-Jordan
2021-10-08 18:54 ` Paolo Bonzini
2021-10-09 5:32 ` Pedro Tôrres
2021-10-10 19:25 ` Paolo Bonzini
2021-10-10 21:22 ` Pedro Tôrres
2021-10-11 13:19 ` Gabriel L. Somlo
2021-10-11 13:40 ` BALATON Zoltan
2021-10-11 14:36 ` Gabriel L. Somlo [this message]
2021-10-13 20:03 ` Phil Dennis-Jordan
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=YWRL2DmlJK3yjV8c@errol.ini.cmu.edu \
--to=gsomlo@gmail.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=balaton@eik.bme.hu \
--cc=f4bug@amsat.org \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=phil@philjordan.eu \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
--cc=suse@csgraf.de \
--cc=t0rr3sp3dr0@gmail.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 NNTP newsgroup(s).