[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZLhG/0HAkX/ZtJTw@google.com>
Date: Wed, 19 Jul 2023 13:26:39 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Weijiang Yang <weijiang.yang@...el.com>
Cc: pbonzini@...hat.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, peterz@...radead.org,
rppt@...nel.org, binbin.wu@...ux.intel.com,
rick.p.edgecombe@...el.com, john.allen@....com,
Chao Gao <chao.gao@...el.com>
Subject: Re: [PATCH v3 00/21] Enable CET Virtualization
On Wed, Jul 19, 2023, Sean Christopherson wrote:
> On Mon, Jul 17, 2023, Weijiang Yang wrote:
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index e2c549f147a5..7d9cfb7e2fe8 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -11212,6 +11212,31 @@ static void kvm_put_guest_fpu(struct kvm_vcpu
> > *vcpu)
> > ������� trace_kvm_fpu(0);
> > �}
Huh. After a bit of debugging, the mangling is due to mutt's default for send_charset
being
"us-ascii:iso-8859-1:utf-8"
and selecting iso-8859-1 instead of utf-8 as the encoding despite the original
mail being utf-8. In this case, mutt ran afoul of nbsp (u+00a0).
AFAICT, the solution is to essentially tell mutt to never try to use iso-8859-1
for sending mail
set send_charset="us-ascii:utf-8"
Powered by blists - more mailing lists