From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8C897C28CBC for ; Wed, 6 May 2020 08:46:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2F34F206D5 for ; Wed, 6 May 2020 08:46:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=yandex-team.ru header.i=@yandex-team.ru header.b="grlUZ1Uq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729006AbgEFIqY (ORCPT ); Wed, 6 May 2020 04:46:24 -0400 Received: from forwardcorp1j.mail.yandex.net ([5.45.199.163]:44582 "EHLO forwardcorp1j.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728511AbgEFIqX (ORCPT ); Wed, 6 May 2020 04:46:23 -0400 Received: from mxbackcorp1o.mail.yandex.net (mxbackcorp1o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::301]) by forwardcorp1j.mail.yandex.net (Yandex) with ESMTP id CF01F2E14AC; Wed, 6 May 2020 11:46:20 +0300 (MSK) Received: from myt5-70c90f7d6d7d.qloud-c.yandex.net (myt5-70c90f7d6d7d.qloud-c.yandex.net [2a02:6b8:c12:3e2c:0:640:70c9:f7d]) by mxbackcorp1o.mail.yandex.net (mxbackcorp/Yandex) with ESMTP id 8lWMk1HLlf-kGb8PuG7; Wed, 06 May 2020 11:46:20 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1588754780; bh=tzipwafqwMZKcvDRA5wYvzE0sK16bTgRO8O/S+yW0cg=; h=In-Reply-To:Message-ID:Subject:To:From:References:Date:Cc; b=grlUZ1Uq7wY0xGJFbdO9mpus4qCf4hY98vTc8rTJc+TPBalL9J/HkfQ1wlsAjzi3m vN+XSBB+OaF9rtlSbnXIFJgjSvXSHP9lAt2GbR/ZxDvwypn8tFF+WrE0mql6tP9u88 IKtnuVtXjTdNG2Dr0o1ZYuEfpfwvpG220dMDRTbw= Authentication-Results: mxbackcorp1o.mail.yandex.net; dkim=pass header.i=@yandex-team.ru Received: from dynamic-vpn.dhcp.yndx.net (dynamic-vpn.dhcp.yndx.net [2a02:6b8:b080:6907::1:5]) by myt5-70c90f7d6d7d.qloud-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id 2GB9My1rM5-kGWSs5Qw; Wed, 06 May 2020 11:46:16 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Wed, 6 May 2020 11:46:15 +0300 From: Roman Kagan To: Jon Doron Cc: Vitaly Kuznetsov , kvm@vger.kernel.org, linux-hyperv@vger.kernel.org Subject: Re: [PATCH v2 0/1] x86/kvm/hyper-v: Add support to SYNIC exit on EOM Message-ID: <20200506084615.GA32841@rvkaganb> Mail-Followup-To: Roman Kagan , Jon Doron , Vitaly Kuznetsov , kvm@vger.kernel.org, linux-hyperv@vger.kernel.org References: <20200417104251.GA3009@rvkaganb> <20200418064127.GB1917435@jondnuc> <20200424133742.GA2439920@rvkaganb> <20200425061637.GF1917435@jondnuc> <20200503191900.GA389956@rvkaganb> <87a72nelup.fsf@vitty.brq.redhat.com> <20200505080158.GA400685@rvkaganb> <20200505103821.GB2862@jondnuc> <20200505200010.GB400685@rvkaganb> <20200506044929.GD2862@jondnuc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200506044929.GD2862@jondnuc> Sender: linux-hyperv-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On Wed, May 06, 2020 at 07:49:29AM +0300, Jon Doron wrote: > Thanks Roman, I see your point, it's important for me to get the EDK2 > working properly not sure why it's not working for me. As I wrote a good deal of that code I hope I should be able to help (and I'd be interested, too). How exactly does the "not working" look like? Also I'm a bit confused as to why UEFI is critical for the work you're doing? Can't it be made to work with BIOS first? > Do you know by any chance if the EDK2 hyperv patches were submitted and if > they were why they were not merged in? I do, as I'm probably the only one who could have submitted them :) No they were not submitted. Neither were the ones for SeaBIOS nor iPXE. The reason was that I had found no way to use alternative firmware with HyperV, so the only environment where that would be useful and testable was QEMU with VMBus. Therefore I thought it made no sense to submit them until VMBus landed in QEMU. Thanks, Roman.