All of lore.kernel.org
 help / color / mirror / Atom feed
From: leohou <leohou1402@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: 回复: Fw: 来自Leo Hou的邮件
Date: Thu, 2 Nov 2023 13:36:04 +0800	[thread overview]
Message-ID: <e96c2abc-ead3-4b3b-992e-e5a2c48a8fa3@gmail.com> (raw)
In-Reply-To: <0a514711-41cc-43ec-ba2d-16109eae783d@gmail.com>

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.


      reply	other threads:[~2023-11-02  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 message]

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=e96c2abc-ead3-4b3b-992e-e5a2c48a8fa3@gmail.com \
    --to=leohou1402@gmail.com \
    --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 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.