From: Ingo Molnar <mingo@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] irq: core changes for x86 ioapic hotplug
Date: Wed, 7 May 2014 11:46:02 +0200 [thread overview]
Message-ID: <20140507094602.GA17560@gmail.com> (raw)
In-Reply-To: <1399340006-31550-1-git-send-email-yinghai@kernel.org>
* Yinghai Lu <yinghai@kernel.org> wrote:
> Hi,
>
> These patches are core changes for x86 ioapic hotplug support.
>
> First part for kill old irq_reserve_irqs:
> During reviewing ioapic hotplug patchset, Thomas pointed out that
> should not extend irq_reserve_irq for that purpose as that is not
> actually reserve.
> Neet to clean up old irq_reserve_irq before introduce reserve/alloc_reserved
> method for ioapic hotplug.
> So here patchset that kill irq_reserve_irq that actually set allocated_irqs.
> First remove irq_reserve_irqs for x86, and remove irq_reserve_irq
> for sh.
> Then in set_irq_chip use irq_alloc_desc instead of irq_reserve_irq.
> Next will mark bits in allocated_irqs early for init irqs in !SPARSE_IRQ
>
> Second parts are new reserve/alloc_reserved functions:
> It will introduce reserved_irqs bit maps to track reserved irqs.
> New irq_alloc_reserved_desc() will only allocate desc when that irq
> is reserved, at the same time irq_alloc_desc will only allocate desc
> when irq is not reserved.
That's not a proper description of the problem and the solution. The
same problem of lack of proper explanation permeates most of your
patches as well and that's very far from the quality threshold that
core IRQ patches need to meet.
Crappy descriptions and passive-aggressive responses where you pretend
you don't understand our complaints and just minimally address the
problems are not acceptable.
So I concur with Thomas and this series earns a big fat NAK from me.
(Please Cc: me to all (if any) future resubmissions so I can track
progress (or the lack thereof) and see whether I can lift my NAK.)
Thanks,
Ingo
prev parent reply other threads:[~2014-05-07 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 1:33 [PATCH v3 0/8] irq: core changes for x86 ioapic hotplug Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 1/8] x86, irq: Remove not needed irq_reserve_irqs calling Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 2/8] sh, irq: Remove irq_reserve_irq calling Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 3/8] irq: Use irq_alloc_desc_at instead of irq_reserve_irq Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 4/8] s390: Mark bits in allocated_irqs in general code Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 5/8] irq: Kill irq_reserve_irq/irq_reserve_irqs Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 6/8] irq: Add new reserved_irqs clear/mark functions Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 7/8] irq: Add irq_alloc_reserved_desc() Yinghai Lu
2014-05-06 1:33 ` [PATCH v3 8/8] irq: Do not free unallocated irq descriptors Yinghai Lu
2014-05-07 9:46 ` Ingo Molnar [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=20140507094602.GA17560@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=yinghai@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