* 回复: Fw: 来自Leo Hou的邮件
[not found] <3ab81ab1.1faf.18b8df8f26e.Coremail.leohou163@163.com>
@ 2023-11-02 3:33 ` leohou1402
2023-11-02 4:46 ` leohou
0 siblings, 1 reply; 3+ messages in thread
From: leohou1402 @ 2023-11-02 3:33 UTC (permalink / raw)
To: philmd; +Cc: qemu-devel
On 31/10/23 16:13:32 Philippe Mathieu-Daudé wrote:
>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/)
Hi Philippe
Thank you for your reply. I didn't check my email in time
because of the mailbox problem. Now I will reply to you
by changing my email address.
With regard to your discussion, is it convenient to announce
the results of the discussion now?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 回复: Fw: 来自Leo Hou的邮件
2023-11-02 3:33 ` 回复: Fw: 来自Leo Hou的邮件 leohou1402
@ 2023-11-02 4:46 ` leohou
2023-11-02 5:36 ` leohou
0 siblings, 1 reply; 3+ messages in thread
From: leohou @ 2023-11-02 4:46 UTC (permalink / raw)
To: qemu-devel
On 2023/11/2 11:33, leohou1402@gmail.com wrote:
> On 31/10/23 16:13:32 Philippe Mathieu-Daudé wrote:
>> 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/)
>
> Hi Philippe
>
>
> Thank you for your reply. I didn't check my email in time
> because of the mailbox problem. Now I will reply to you
> by changing my email address.
>
> With regard to your discussion, is it convenient to announce
> the results of the discussion now?
Is there a need for the architecture of the main cpu and several
coprocessors?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 回复: Fw: 来自Leo Hou的邮件
2023-11-02 4:46 ` leohou
@ 2023-11-02 5:36 ` leohou
0 siblings, 0 replies; 3+ messages in thread
From: leohou @ 2023-11-02 5:36 UTC (permalink / raw)
To: qemu-devel
On 2023/11/2 12:46, leohou wrote:
> On 2023/11/2 11:33, leohou1402@gmail.com wrote:
>> On 31/10/23 16:13:32 Philippe Mathieu-Daudé wrote:
>>> 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/)
>>>
>>
>> Hi Philippe
>>
>>
>> Thank you for your reply. I didn't check my email in time
>> because of the mailbox problem. Now I will reply to you
>> by changing my email address.
>>
>> With regard to your discussion, is it convenient to announce
>> the results of the discussion now?
>
> Is there a need for the architecture of the main cpu and several
> coprocessors?
>
>
Examples include SCP and MCP in the ARM N2 platform, or an ARM host
machine containing a risc-v coprocessor.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-11-02 5:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <3ab81ab1.1faf.18b8df8f26e.Coremail.leohou163@163.com>
2023-11-02 3:33 ` 回复: Fw: 来自Leo Hou的邮件 leohou1402
2023-11-02 4:46 ` leohou
2023-11-02 5:36 ` leohou
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).