mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jim Mattson <jmattson@google.com>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: linux-next: Tree for Mar 9
Date: Mon, 9 Mar 2026 14:53:21 -0700	[thread overview]
Message-ID: <69576db3-352c-41fd-a96e-a1bc6ed7b74b@infradead.org> (raw)
In-Reply-To: <aa8WV_KvEV_TFPPZ@sirena.org.uk>



On 3/9/26 11:49 AM, Mark Brown wrote:
> Hi all,
> 
> Changes since 20260306:
> 

for linux-next 2026030[459]:

linux-next/Documentation/virt/kvm/api.rst:8547: ERROR: Malformed table.
Text in column margin in table line 110.

=================================== ============================================
 KVM_X86_QUIRK_LINT0_REENABLED      By default, the reset value for the LVT
                                    LINT0 register is 0x700 (APIC_MODE_EXTINT).
                                    When this quirk is disabled, the reset value
                                    is 0x10000 (APIC_LVT_MASKED).
...
KVM_X86_QUIRK_VMCS12_FREEZE_IN_SMM_CC By default, KVM relaxes the consistency
                                      check for GUEST_IA32_DEBUGCTL in vmcs12
                                      to allow FREEZE_IN_SMM to be set.  When
                                      this quirk is disabled, KVM requires this
                                      bit to be cleared.  Note that the vmcs02
                                      bit is still completely controlled by the
                                      host, regardless of the quirk setting.
=================================== ============================================

The last table entry does not fit into the table's "columns".

From:
commit 0f70db0758be
Author: Jim Mattson <jmattson@google.com>
Date:   Thu Feb 5 15:15:26 2026 -0800
    KVM: x86: Introduce KVM_X86_QUIRK_VMCS12_FREEZE_IN_SMM_CC


-- 
~Randy


  parent reply	other threads:[~2026-03-09 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 18:49 Mark Brown
2026-03-09 19:51 ` Andy Shevchenko
2026-03-09 19:52   ` Mark Brown
2026-03-09 21:53 ` Randy Dunlap [this message]
2026-03-10  3:50 ` linux-next: Tree for Mar 9 (ntfs) Randy Dunlap
2026-03-10  4:05   ` Namjae Jeon
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  1:46 linux-next: Tree for Mar 9 Stephen Rothwell
2022-03-09 11:53 Stephen Rothwell
2021-03-09  3:56 Stephen Rothwell
2018-03-09  4:30 Stephen Rothwell
2018-03-09  5:07 ` Stephen Rothwell
2017-03-09  2:45 Stephen Rothwell
2016-03-09  5:38 Stephen Rothwell
2012-03-09  8:11 Stephen Rothwell

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=69576db3-352c-41fd-a96e-a1bc6ed7b74b@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=broonie@kernel.org \
    --cc=jmattson@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=seanjc@google.com \
    /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

all inboxes | Powered by JetHome®