From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web10.27782.1683625340131253640 for ; Tue, 09 May 2023 02:42:20 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SegiUi3Z; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683625339; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=35mddilXi6nixxUT0L9gfWpfVwmMVvxvfJZTOq1upsk=; b=SegiUi3ZhLZ0J72AjuOkBpyB1F4daiB9tZIvqrGcNVAomVjavTPJzTrwOrhB9xJhBtrkHN ewQ8SL2beBecKAlAyQmD4GM+mrZiMWPx5/g5yU9XVroVtURBacuk4JevCFVyb1/+o1EZis k31GMInVxbRfMmWGV/Lde8onKgjem00= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-122-ntW7_ueFNBen2PMXKGMtMw-1; Tue, 09 May 2023 05:42:17 -0400 X-MC-Unique: ntW7_ueFNBen2PMXKGMtMw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 01F53886462; Tue, 9 May 2023 09:42:17 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.221]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C31E21410DD5; Tue, 9 May 2023 09:42:16 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 681C81801081; Tue, 9 May 2023 11:42:15 +0200 (CEST) Date: Tue, 9 May 2023 11:42:15 +0200 From: "Gerd Hoffmann" To: Laszlo Ersek Cc: Michael Brown , devel@edk2.groups.io Subject: Re: [PATCH 2/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL Message-ID: References: <476bbc17-6484-9afd-9be9-08de14d1d72e@redhat.com> <20230508213100.3949708-1-mcb30@ipxe.org> <01020187fd46e7d4-9dba3e15-efcc-4ea7-87ba-2391a3f372d5-000000@eu-west-1.amazonses.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, > Here's why: I'd been used to Microsoft *not* cooperating usefully in > Windows-on-QEMU/KVM situations. But this instance was totally different. > In fact I'm still a bit shocked, in the positive sense. We got a fast > and helpful, to-the-point response. It's a first, considering my own > experience, and it has strongly changed my impression of Microsoft's > Windows team. I'd like us to acknowledge that in the commit message, if > possible. And Microsoft saying this is tsc calibration code also gives us a workaround: When using 'qemu -cpu host,hv-frequencies=on' the windows installer iso boots just fine, most likely because cdboot.efi queries the hypervisor for the tsc frequency instead of running the calibration loop. take care, Gerd