Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1731480 > unrolled thread
| Started by | Ingo Molnar <mingo@kernel.org> |
|---|---|
| First post | 2017-09-13 11:10 +0200 |
| Last post | 2017-09-13 20:10 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot Ingo Molnar <mingo@kernel.org> - 2017-09-13 11:10 +0200
RE: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot KY Srinivasan <kys@microsoft.com> - 2017-09-13 20:10 +0200
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Date | 2017-09-13 11:10 +0200 |
| Subject | Re: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot |
| Message-ID | <upbQd-5mJ-5@gated-at.bofh.it> |
* KY Srinivasan <kys@microsoft.com> wrote: > > > > -----Original Message----- > > From: Dan Carpenter [mailto:dan.carpenter@oracle.com] > > Sent: Saturday, September 9, 2017 4:04 AM > > To: KY Srinivasan <kys@microsoft.com> > > Cc: x86@kernel.org; gregkh@linuxfoundation.org; linux- > > kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de; > > apw@canonical.com; jasowang@redhat.com; tglx@linutronix.de; > > hpa@zytor.com; mingo@kernel.org > > Subject: Re: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot > > > > On Fri, Sep 08, 2017 at 04:15:57PM -0700, kys@exchange.microsoft.com > > wrote: > > > From: "K. Y. Srinivasan" <kys@microsoft.com> > > > > > > Allocate the hypervisor callback IDT entry early in the boot sequence. > > > > > > > I'm guessing this fixes a NULL dereference or something? The changelog > > doesn't really say why we are doing this. > > The changelog does say what we are doing - allocating the IDT entry early in the boot sequence. But the question was the 'why', not the 'what' - so Dan's question is fully justified ... > The current code would allocate the entry as part of registering the handler > when vmbus driver loaded and this caused a problem for the cleanup Thomas had > implemented. I've put this explanation into the changelog. Thanks, Ingo
[toc] | [next] | [standalone]
| From | KY Srinivasan <kys@microsoft.com> |
|---|---|
| Date | 2017-09-13 20:10 +0200 |
| Message-ID | <upkgO-2kQ-13@gated-at.bofh.it> |
| In reply to | #1731480 |
> -----Original Message----- > From: Ingo Molnar [mailto:mingo.kernel.org@gmail.com] On Behalf Of Ingo > Molnar > Sent: Wednesday, September 13, 2017 2:01 AM > To: KY Srinivasan <kys@microsoft.com> > Cc: Dan Carpenter <dan.carpenter@oracle.com>; x86@kernel.org; > gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org; > devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com; > jasowang@redhat.com; tglx@linutronix.de; hpa@zytor.com > Subject: Re: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot > > > * KY Srinivasan <kys@microsoft.com> wrote: > > > > > > > > -----Original Message----- > > > From: Dan Carpenter [mailto:dan.carpenter@oracle.com] > > > Sent: Saturday, September 9, 2017 4:04 AM > > > To: KY Srinivasan <kys@microsoft.com> > > > Cc: x86@kernel.org; gregkh@linuxfoundation.org; linux- > > > kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de; > > > apw@canonical.com; jasowang@redhat.com; tglx@linutronix.de; > > > hpa@zytor.com; mingo@kernel.org > > > Subject: Re: [PATCH 1/1] x86/hyper-V: Allocate the IDT entry early in boot > > > > > > On Fri, Sep 08, 2017 at 04:15:57PM -0700, kys@exchange.microsoft.com > > > wrote: > > > > From: "K. Y. Srinivasan" <kys@microsoft.com> > > > > > > > > Allocate the hypervisor callback IDT entry early in the boot sequence. > > > > > > > > > > I'm guessing this fixes a NULL dereference or something? The changelog > > > doesn't really say why we are doing this. > > > > The changelog does say what we are doing - allocating the IDT entry early in > the boot sequence. > > But the question was the 'why', not the 'what' - so Dan's question is > fully justified ... > > > The current code would allocate the entry as part of registering the handler > > when vmbus driver loaded and this caused a problem for the cleanup > Thomas had > > implemented. > > I've put this explanation into the changelog. You are right. Thanks, Ingo. K. Y > > Thanks, > > Ingo
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web