* 来自Leo Hou的邮件
@ 2023-10-31 3:10 Leo Hou
2023-10-31 8:13 ` Philippe Mathieu-Daudé
2023-11-02 1:48 ` 回复: " leohou163
0 siblings, 2 replies; 3+ messages in thread
From: Leo Hou @ 2023-10-31 3:10 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 66 bytes --]
hi , all
Does qemu plan to support CPU heterogeneity?
[-- Attachment #2: Type: text/html, Size: 285 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: 来自Leo Hou的邮件
2023-10-31 3:10 来自Leo Hou的邮件 Leo Hou
@ 2023-10-31 8:13 ` Philippe Mathieu-Daudé
2023-11-02 1:48 ` 回复: " leohou163
1 sibling, 0 replies; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2023-10-31 8:13 UTC (permalink / raw)
To: Leo Hou, qemu-devel; +Cc: qemu-discuss
Hi Leo,
On 31/10/23 04:10, Leo Hou wrote:
> hi , all
> Does qemu plan to support CPU heterogeneity?
Short answer is yes. When will this be available is yet to
be determined, as a lot of work is required.
I'm going to talk about the challenges and possible roadmap
later today, feel free to join the call scheduled at 2pm CET
on https://meet.jit.si/kvmcallmeeting.
(See
https://lore.kernel.org/qemu-devel/calendar-1ad16449-09cc-40fb-ab4a-24eafcc62d2a@google.com/)
Regards,
Phil.
^ permalink raw reply [flat|nested] 3+ messages in thread
* 回复: 来自Leo Hou的邮件
2023-10-31 3:10 来自Leo Hou的邮件 Leo Hou
2023-10-31 8:13 ` Philippe Mathieu-Daudé
@ 2023-11-02 1:48 ` leohou163
1 sibling, 0 replies; 3+ messages in thread
From: leohou163 @ 2023-11-02 1:48 UTC (permalink / raw)
To: qemu-devel
hi , all
Does qemu plan to support CPU heterogeneity?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-11-02 1:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-31 3:10 来自Leo Hou的邮件 Leo Hou
2023-10-31 8:13 ` Philippe Mathieu-Daudé
2023-11-02 1:48 ` 回复: " leohou163
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).