From: Thomas Gleixner <tglx@linutronix.de>
To: Wanpeng Li <wanpeng.li@hotmail.com>
Cc: "Arisetty, Chakravarthy" <Chakravarthy.Arisetty@viasat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Uberoy, Pawan" <Pawan.Uberoy@viasat.com>,
"Mani, Somnath" <Somnath.Mani@viasat.com>,
"Rich, Dennis" <Dennis.Rich@viasat.com>
Subject: Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel
Date: Fri, 26 Jan 2018 07:33:58 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801260731370.2203@nanos> (raw)
In-Reply-To: <SG2PR02MB1312845BD13E8538F881F62780E00@SG2PR02MB1312.apcprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On Fri, 26 Jan 2018, Wanpeng Li wrote:
Folks, can you please stop this corporate email style nonsense?
> On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote:
> >> IIRC,the race which KVM: LAPIC: Fix reentrancy issues with preempt notifiers<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.kernel.org_pub_scm_linux_kernel_git_stable_linux-2Dstable.git_commit_arch_x86_kvm_lapic.c-3Fh-3Dlinux-2D4.13.y-26id-3D1d518c6820daf4e00d29adfba980aee05f605f0f&d=DwMGaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=Ffjvk4Y8xEf_-aLPhDRUD2drOoDsZ0R_uiCBYAvmwAY&m=HxxYRqfeH8SOgZuryI2hIvUXHNgkHkYSOXflazJS-h8&s=Ucf0XMULwrmlqxf5Q-IEoiZVHM1hkEL2Xz5RRCqUmQA&e=> tries to fix is exposed by refactor restart_apic_timer patchset. If you don't care the latency which https://lkml.org/lkml/2017/6/29/604<https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2017_6_29_604&d=DwMGaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=Ffjvk4Y8xEf_-aLPhDRUD2drOoDsZ0R_uiCBYAvmwAY&m=HxxYRqfeH8SOgZuryI2hIvUXHNgkHkYSOXflazJS-h8&s=bdN75Gm8T9CzT4mokKCWPHP8Inl5tibax6aU5mkibBM&e=> patchset tries to reduce, you can ignore the whole patchset and this fix.
>
This is absolutely unreadable gunk. It's enough to refer to a commit sha
instead of these horrible unformatted html style references. And please
stop top posting and trim your replies.
Thanks,
tglx
next parent reply other threads:[~2018-01-26 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18097436-5845-44E4-8CDC-D020C71DFA83@viasat.com>
[not found] ` <SG2PR02MB1312DAE2C0999AF42F380B1680E10@SG2PR02MB1312.apcprd02.prod.outlook.com>
[not found] ` <9C630A72-B122-4200-A480-48BCA1CAB056@viasat.com>
[not found] ` <SG2PR02MB1312845BD13E8538F881F62780E00@SG2PR02MB1312.apcprd02.prod.outlook.com>
2018-01-26 6:33 ` Thomas Gleixner [this message]
2018-01-26 19:10 ` Arisetty, Chakravarthy
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=alpine.DEB.2.20.1801260731370.2203@nanos \
--to=tglx@linutronix.de \
--cc=Chakravarthy.Arisetty@viasat.com \
--cc=Dennis.Rich@viasat.com \
--cc=Pawan.Uberoy@viasat.com \
--cc=Somnath.Mani@viasat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.com \
--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
all inboxes | Powered by JetHome®