From: "Li, Xin3" <xin3.li@intel.com>
To: "Li, Xin3" <xin3.li@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"brgerst@gmail.com" <brgerst@gmail.com>,
"Bae, Chang Seok" <chang.seok.bae@intel.com>
Subject: RE: [PATCH v4 0/5] x86: Enable LKGS instruction
Date: Fri, 18 Nov 2022 07:25:14 +0000 [thread overview]
Message-ID: <BN6PR1101MB216139DE17AE8AABBEF0BCD0A8099@BN6PR1101MB2161.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN6PR1101MB216116E243237CDABFE77B3AA82B9@BN6PR1101MB2161.namprd11.prod.outlook.com>
> > On Wed, Oct 19 2022 at 03:23, Xin Li wrote:
> > > LKGS instruction is introduced with Intel FRED (flexible return and
> > > event
> > > delivery) specification https://cdrdv2.intel.com/v1/dl/getContent/678938.
> >
> > So I have two versions of the same thing in my inbox now. What's the
> > difference?
Hi Thomas,
Should I resend it?
Xin
>
> No difference at all.
>
> Sorry for the confusion, but maybe I have an excuse. A few days ago, I sent an
> email to the LKML and it seems lost. I got to know it until Nathan Chancellor
> replied; and my original message doesn't show up here:
> https://lore.kernel.org/all/Y02eZ6A%2Fvlj8+B%2Fc@dev-arch.thelio-3990X/
>
> Last night I sent this patch set to the LKML and waited half an hour, they still
> didn't show up, so I did it again, but this time both worked.
>
> I have sent an email to owner-linux-kernel@vger.kernel.org asking for help.
>
> Xin
prev parent reply other threads:[~2022-11-18 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 10:23 [PATCH v4 0/5] x86: Enable LKGS instruction Xin Li
2022-10-19 10:23 ` [PATCH v4 1/5] x86/cpufeature: add the cpu feature bit for LKGS Xin Li
2022-10-19 10:23 ` [PATCH v4 2/5] x86/opcode: add the LKGS instruction to x86-opcode-map Xin Li
2022-10-19 10:23 ` [PATCH v4 3/5] x86/gsseg: make asm_load_gs_index() take an u16 Xin Li
2022-10-19 10:23 ` [PATCH v4 4/5] x86/gsseg: move load_gs_index() to its own new header file Xin Li
2022-10-19 10:23 ` [PATCH v4 5/5] x86/gsseg: use the LKGS instruction if available for load_gs_index() Xin Li
2022-10-19 14:12 ` [PATCH v4 0/5] x86: Enable LKGS instruction Thomas Gleixner
2022-10-19 17:03 ` Li, Xin3
2022-11-18 7:25 ` Li, Xin3 [this message]
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=BN6PR1101MB216139DE17AE8AABBEF0BCD0A8099@BN6PR1101MB2161.namprd11.prod.outlook.com \
--to=xin3.li@intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).