From: Timur Tabi <timur@codeaurora.org>
To: Sinan Kaya <okaya@codeaurora.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
linux-acpi@vger.kernel.org, cov@codeaurora.org, jcm@redhat.com
Cc: agross@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: add support for extended IRQ to PCI link
Date: Mon, 9 Nov 2015 07:50:48 -0600 [thread overview]
Message-ID: <5640A4B8.9020602@codeaurora.org> (raw)
In-Reply-To: <56403311.2020806@codeaurora.org>
Sinan Kaya wrote:
>
> I'm concerned about this though since you warned. This used to consume
> 1024 bytes now 4096 bytes.
>
> static int acpi_irq_penalty[ACPI_MAX_IRQS] = {
> PIRQ_PENALTY_ISA_ALWAYS, /* IRQ0 timer */
> ...
> }
As long as it's not ever put on the stack, it should be fine.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] acpi: add support for extended IRQ to PCI link
Date: Mon, 9 Nov 2015 07:50:48 -0600 [thread overview]
Message-ID: <5640A4B8.9020602@codeaurora.org> (raw)
In-Reply-To: <56403311.2020806@codeaurora.org>
Sinan Kaya wrote:
>
> I'm concerned about this though since you warned. This used to consume
> 1024 bytes now 4096 bytes.
>
> static int acpi_irq_penalty[ACPI_MAX_IRQS] = {
> PIRQ_PENALTY_ISA_ALWAYS, /* IRQ0 timer */
> ...
> }
As long as it's not ever put on the stack, it should be fine.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
next prev parent reply other threads:[~2015-11-09 13:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:07 [PATCH] acpi: add support for extended IRQ to PCI link Sinan Kaya
2015-11-08 16:07 ` Sinan Kaya
2015-11-08 16:11 ` Timur Tabi
2015-11-08 16:11 ` Timur Tabi
2015-11-09 0:04 ` Sinan Kaya
2015-11-09 0:04 ` Sinan Kaya
2015-11-09 0:05 ` Timur Tabi
2015-11-09 0:05 ` Timur Tabi
2015-11-09 21:49 ` Rafael J. Wysocki
2015-11-09 21:49 ` Rafael J. Wysocki
2015-11-08 20:35 ` Andy Shevchenko
2015-11-08 20:35 ` Andy Shevchenko
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 5:24 ` Jiang Liu
2015-11-09 5:24 ` Jiang Liu
2015-11-09 5:45 ` Sinan Kaya
2015-11-09 5:45 ` Sinan Kaya
2015-11-09 8:45 ` Jiang Liu
2015-11-09 8:45 ` Jiang Liu
2015-11-09 13:50 ` Timur Tabi [this message]
2015-11-09 13:50 ` Timur Tabi
2015-11-09 16:28 ` Sinan Kaya
2015-11-09 16:28 ` Sinan Kaya
2015-11-12 6:14 [PATCH V2] " Sinan Kaya
2015-11-12 6:14 ` [PATCH] " Sinan Kaya
2015-11-12 9:56 ` Andy Shevchenko
2015-11-12 15:04 ` Sinan Kaya
2015-11-12 15:17 ` Andy Shevchenko
2015-11-12 15:54 ` okaya
2015-11-12 15:58 ` Timur Tabi
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=5640A4B8.9020602@codeaurora.org \
--to=timur@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=cov@codeaurora.org \
--cc=jcm@redhat.com \
--cc=jiang.liu@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=rjw@rjwysocki.net \
/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.