From: Borislav Petkov <bp@alien8.de>
To: hch <hch@lst.de>
Cc: Richard Weinberger <richard@nod.at>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
x86 <x86@kernel.org>, linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: remove set_fs for UML
Date: Wed, 22 Dec 2021 14:55:39 +0100 [thread overview]
Message-ID: <YcMuW88cOBNXAdb/@zn.tnic> (raw)
In-Reply-To: <20211222081753.GB22041@lst.de>
On Wed, Dec 22, 2021 at 09:17:53AM +0100, hch wrote:
> On Tue, Dec 21, 2021 at 10:05:03PM +0100, Richard Weinberger wrote:
> > So far UML seems to work with these changes applied. :-)
> > I have applied both patches to my UML tree for now, I assume x86 maintainers are fine with
> > patch 1/2?
>
> Looks like patch 1 needs this fixup for some configurations, where
> pci.h doesn't get pulled into kvm by other means.
>
> But we probably want an ACK from the x86 maintainers to be sure anyway..
I don't see why not so
Acked-by: Borislav Petkov <bp@suse.de>
Should I take the first one along with this hunk below?
> diff --git a/arch/x86/kvm/mmu/spte.c b/arch/x86/kvm/mmu/spte.c
> index 0c76c45fdb686..fad546df0bbac 100644
> --- a/arch/x86/kvm/mmu/spte.c
> +++ b/arch/x86/kvm/mmu/spte.c
> @@ -16,6 +16,7 @@
> #include "spte.h"
>
> #include <asm/e820/api.h>
> +#include <asm/memtype.h>
> #include <asm/vmx.h>
>
> static bool __read_mostly enable_mmio_caching = true;
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: hch <hch@lst.de>
Cc: Richard Weinberger <richard@nod.at>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
x86 <x86@kernel.org>, linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: remove set_fs for UML
Date: Wed, 22 Dec 2021 14:55:39 +0100 [thread overview]
Message-ID: <YcMuW88cOBNXAdb/@zn.tnic> (raw)
In-Reply-To: <20211222081753.GB22041@lst.de>
On Wed, Dec 22, 2021 at 09:17:53AM +0100, hch wrote:
> On Tue, Dec 21, 2021 at 10:05:03PM +0100, Richard Weinberger wrote:
> > So far UML seems to work with these changes applied. :-)
> > I have applied both patches to my UML tree for now, I assume x86 maintainers are fine with
> > patch 1/2?
>
> Looks like patch 1 needs this fixup for some configurations, where
> pci.h doesn't get pulled into kvm by other means.
>
> But we probably want an ACK from the x86 maintainers to be sure anyway..
I don't see why not so
Acked-by: Borislav Petkov <bp@suse.de>
Should I take the first one along with this hunk below?
> diff --git a/arch/x86/kvm/mmu/spte.c b/arch/x86/kvm/mmu/spte.c
> index 0c76c45fdb686..fad546df0bbac 100644
> --- a/arch/x86/kvm/mmu/spte.c
> +++ b/arch/x86/kvm/mmu/spte.c
> @@ -16,6 +16,7 @@
> #include "spte.h"
>
> #include <asm/e820/api.h>
> +#include <asm/memtype.h>
> #include <asm/vmx.h>
>
> static bool __read_mostly enable_mmio_caching = true;
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-12-22 13:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:56 remove set_fs for UML Christoph Hellwig
2021-12-15 16:56 ` Christoph Hellwig
2021-12-15 16:56 ` [PATCH 1/2] x86/mtrr: remove the mtrr_bp_init stub Christoph Hellwig
2021-12-15 16:56 ` Christoph Hellwig
2021-12-22 18:56 ` [tip: x86/misc] x86/mtrr: Remove the mtrr_bp_init() stub tip-bot2 for Christoph Hellwig
2021-12-15 16:56 ` [PATCH 2/2] um: remove set_fs Christoph Hellwig
2021-12-15 16:56 ` Christoph Hellwig
2021-12-21 21:05 ` remove set_fs for UML Richard Weinberger
2021-12-21 21:05 ` Richard Weinberger
2021-12-22 8:17 ` hch
2021-12-22 8:17 ` hch
2021-12-22 13:55 ` Borislav Petkov [this message]
2021-12-22 13:55 ` Borislav Petkov
2021-12-22 16:55 ` Richard Weinberger
2021-12-22 16:55 ` Richard Weinberger
2021-12-22 18:54 ` Borislav Petkov
2021-12-22 18:54 ` Borislav Petkov
2022-01-01 0:12 ` Al Viro
2022-01-01 0:12 ` Al Viro
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=YcMuW88cOBNXAdb/@zn.tnic \
--to=bp@alien8.de \
--cc=anton.ivanov@cambridgegreys.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.