mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Marc Zyngier <marc.zyngier@arm.com>
Subject: [PATCH 0/2] irqchip/gic-v3-its: a raw_spinlock_t + early ->pend_page allocateion
Date: Wed, 18 Jul 2018 17:42:03 +0200	[thread overview]
Message-ID: <20180718154205.13704-1-bigeasy@linutronix.de> (raw)

The errors popped up in -RT. One is the spinlock_t usage in IRQ-off
region which should be a raw_spinlock_t. I don't see this to be used
during run-time or for long period of time so I don't thing this is an
issue.

The second problem is the ->pend_page allocation on the target_cpu early
during CPU bring up. It would be simpler to allocate the memory once on
the boot CPU instead the hotplug callback since the memory is never
free()ed. I *think* this is avoided because the number of possible CPUs
might be higher than what will actually come up (on x86 the BIOS
sometimes reports more possible_cpus than what is *really* possible, not
sure if ARM64 is there yet). Therefore I moved the allocation to an
earlier callback.

Sebastian


             reply	other threads:[~2018-07-18 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 15:42 Sebastian Andrzej Siewior [this message]
2018-07-18 15:42 ` [PATCH 1/2] irqchip/gic-v3-its: Make its_lock a raw_spin_lock_t Sebastian Andrzej Siewior
2018-08-06  8:17   ` Marc Zyngier
2018-07-18 15:42 ` [PATCH 2/2] irqchip/gic-v3-its: Move ITS' ->pend_page allocation into an early CPU up callback Sebastian Andrzej Siewior
2018-08-06  8:15   ` Marc Zyngier
2018-08-29 16:49     ` Sebastian Andrzej Siewior
2018-08-31 19:32       ` Sebastian Andrzej Siewior

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=20180718154205.13704-1-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®