linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Pilmore <epilmore@gigaio.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	linux-hotplug@vger.kernel.org, D Meyer <dmeyer@gigaio.com>
Subject: Re: PSA: migrating linux-hotplug to new vger infrastructure
Date: Mon, 6 Nov 2023 11:05:47 -0800	[thread overview]
Message-ID: <CAOQPn8vh36KVYNiH=u_rR_PDd1xMoNKuDJ=u1nnGMqFR9un+yg@mail.gmail.com> (raw)
In-Reply-To: <2023110646-unimpeded-palm-e067@gregkh>

On Mon, Nov 6, 2023 at 5:44 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
>
> I think the list can just be deleted, there's no traffic anymore, and
> "hotplug" doesn't make any sense anymore as "everything" can be
> added/removed from a Linux system these days.
>
> So can we just remove it?
>
> thanks,
>
> greg k-h

Hi Greg,

I was curious about your comment regarding "everything". Is it
possible to dynamically add/remove entire I/O sub-trees on the PCIe
side? In other words, can a PCIe bridge, and all associated
sub-branches be dynamically added/removed? If so, is there special
BIOS support required for possibly reserving adequate MMIO address
space?

Thanks,
Eric

  parent reply	other threads:[~2023-11-06 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 13:21 PSA: migrating linux-hotplug to new vger infrastructure Konstantin Ryabitsev
2023-11-06 13:33 ` Greg KH
2023-11-06 14:29   ` Konstantin Ryabitsev
2023-11-06 16:35     ` Greg KH
2023-11-06 19:05   ` Eric Pilmore [this message]
2023-11-06 19:25     ` Greg KH
2023-11-06 20:46       ` Matthew Dharm
2023-11-07  5:12         ` Eric Pilmore
2023-11-07  6:00           ` Greg KH

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='CAOQPn8vh36KVYNiH=u_rR_PDd1xMoNKuDJ=u1nnGMqFR9un+yg@mail.gmail.com' \
    --to=epilmore@gigaio.com \
    --cc=dmeyer@gigaio.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-hotplug@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).