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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1D85EC001DE for ; Fri, 11 Aug 2023 14:30:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235266AbjHKOaa (ORCPT ); Fri, 11 Aug 2023 10:30:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51306 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229706AbjHKOa3 (ORCPT ); Fri, 11 Aug 2023 10:30:29 -0400 Received: from mail-yb1-xb49.google.com (mail-yb1-xb49.google.com [IPv6:2607:f8b0:4864:20::b49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 647FE2D79 for ; Fri, 11 Aug 2023 07:30:28 -0700 (PDT) Received: by mail-yb1-xb49.google.com with SMTP id 3f1490d57ef6-d6280158f50so2169137276.3 for ; Fri, 11 Aug 2023 07:30:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1691764227; x=1692369027; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=d+GMD8mZlyVfifzv/ndRqn1h4dvoCt7rexnp0s7wl+8=; b=hBVWGZz8qhFlB4iGeCj2O9bRCIGDd8+iGa2V9DdR+8YSSuTq44QEMxH4UVb5z3KcGl SvGCKaOPbr9W4BtIeqRv4WmD1287D/eAI+SkNlraRS+gpJImllMfuEjyLI2B6FtrEIw6 uF/7V19VRBhOKn16x5RklcaE2kTLEiuavBEa0CrfFx8kGMhqQR99O35J0JM8sngsUzBx N6in0eb6zmIm0QIGytHJ0wg4CRF6TzQJLytnF9XO7OqGRnF4WfL0uI5tiNYPLpN4OLX5 +VEFVl4I1VL/pu8ijYAu1hUY8QpDz2DQouGaFH4FAqepCDE60kJ//RVJhjVcGY5DuDRp UdEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691764227; x=1692369027; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=d+GMD8mZlyVfifzv/ndRqn1h4dvoCt7rexnp0s7wl+8=; b=V4r55tSG6WhwByPEZAVLv78lVy5FPmP0kw/wKWWwDlLryjJj3qxeShLIJpcI+Fl766 HMw5D7jRSi5RSIefEOjtoBRcnvTLJk/qDfk7DXyWV27p6UDrAnTvSXz1wgKQxVAIm522 rJ9hwoof1YcsIPAby8uz8QQsP1xy81iJQbp+tQaVlAyv76IJU1JkpQHuAqgwEyVgpqY+ Y5Qk7A2H/sYpJGfsdyOp9jfZX2shTw7qZK665GkBE7gLuDAGv1W8Q7FOJQdN/f67d9fT bmyVoLnwylNZs/hJVck18C6ikhIFtxDrpYLCNRHm6Eu2nNEpOXW6PH919BKTCzquzWKi 1Fmg== X-Gm-Message-State: AOJu0YxMb+WH5x5nYAMxw1HdFk3eAQiZkUhT9LJs4ELRUrN2mjcVAzff meHqdC50hXSdeZajQoSo6iJSI/nCy8g= X-Google-Smtp-Source: AGHT+IE33lrnYvERPkhF79oAVBOVoEU3v59dJ2RthpMsPnbew0iZgxB0b5RWhHlOBnyqVfyaO4Aw4ONjGOs= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:6854:0:b0:d05:7ba4:67f9 with SMTP id d81-20020a256854000000b00d057ba467f9mr32202ybc.3.1691764227710; Fri, 11 Aug 2023 07:30:27 -0700 (PDT) Date: Fri, 11 Aug 2023 07:30:25 -0700 In-Reply-To: Mime-Version: 1.0 References: Message-ID: Subject: Re: next-20230809: kvm unittest fail: emulator From: Sean Christopherson To: Srikanth Aithal Cc: kvm@vger.kernel.org, linux-next@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Fri, Aug 11, 2023, Srikanth Aithal wrote: > On 8/11/2023 4:15 AM, Sean Christopherson wrote: > > On Thu, Aug 10, 2023, Srikanth Aithal wrote: > > > Hello, > > > > > > On linux-next 20230809 build kvm emulator unittest failed. > > > > > > =================== > > > Recreation steps: > > > =================== > > > > > > 1. git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git > > > 2. export QEMU= I used v8.0.2 > > > 3. cd kvm-unit-tests/;./configure;make standalone;tests/emulator > > > > What hardware are you running on? I've tested on a variety of hardware, Intel > > and AMD, and haven't observed any problems. > I am running it on Dell PowerEdge r6515. Same tests were passing till > next-20230808. Ah, let me try an actual linux-next build (once I get the darn thing to compile). I was assuming I broke something in kvm-x86/next and so was testing that. But I haven't pushed to kvm-x86/next since 08/03, so presumably the bug came in from somewhere else. Ugh, it's probably one of the recent mitigations. Those things always break stuff due to getting thrown in without going through the usual channels.