public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Tiger Liu <TigerLiu@zhaoxin.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: [OVMF] OVMF Support Dual-Socket boot?
Date: Wed, 1 Mar 2017 10:11:04 +0000	[thread overview]
Message-ID: <1E4DA6F54C53C24B98E8E8D172B945AF87720D@ZXBJMBX02.zhaoxin.com> (raw)

Hi, Laszlo:
Thanks for your reply!

So, dual-socket means two pci host bridges exist, and also means two pci segments exist.
Could current Ovmf pci related drivers handle them?

best wishes,

-----邮件原件-----
发件人: Laszlo Ersek [mailto:lersek@redhat.com]
发送时间: 2017年3月1日 17:37
收件人: Tiger Liu
抄送: edk2-devel@lists.01.org
主题: Re: [edk2] [OVMF] OVMF Support Dual-Socket boot?

On 03/01/17 07:06, Tiger Liu wrote:
> Hi, Experts:
> I have a question about dual-socket.
>
> Does Ovmf FW supports Dual-Socket platform boot?

Yes, it does.

> Such as:
> Qemu emulates a dual-socket xeon platform, Could Ovmf UEFI Code boot on it?

I think all of my long-term OVMF guests are SMP (4 or 8 VCPUs generally, on my laptop at least).

Thanks
Laszlo


保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

             reply	other threads:[~2017-03-01 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:11 Tiger Liu [this message]
2017-03-01 18:25 ` [OVMF] OVMF Support Dual-Socket boot? Laszlo Ersek
2017-03-02  1:01   ` 答复: " Tiger Liu
  -- strict thread matches above, loose matches on Subject: below --
2017-03-01  6:06 Tiger Liu
2017-03-01  9:37 ` Laszlo Ersek

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-list 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=1E4DA6F54C53C24B98E8E8D172B945AF87720D@ZXBJMBX02.zhaoxin.com \
    --to=devel@edk2.groups.io \
    /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