From: Yijing Wang <wangyijing@huawei.com>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: sysfs-pci remove
Date: Wed, 17 Dec 2014 13:50:33 +0800 [thread overview]
Message-ID: <549119A9.4010406@huawei.com> (raw)
In-Reply-To: <CAGZFCEFOiY+VmTVKOnPwDaKUKogUX9gkXtHuMATL3btw4kz2JQ@mail.gmail.com>
On 2014/12/17 13:21, ratheesh kannoth wrote:
> I could see the pci resource in /proc/iomem.
>
> But , lspci -s 06:0.0 -vv shows that there is no kernel mode driver
> for that interface.
If the device 06:0.0 was removed by "echo 1 > /sys/.../0000:6:0.0/remove",
you could not see lspci info for this device anymore.
Do you really remove the device ?
>
>
> On Wed, Dec 17, 2014 at 6:30 AM, Yijing Wang <wangyijing@huawei.com> wrote:
>> On 2014/12/17 1:51, ratheesh kannoth wrote:
>>> Hi list,
>>>
>>> https://www.kernel.org/doc/Documentation/filesystems/sysfs-pci.txt
>>> talks about "remove" entry.
>>> The 'remove' file is used to remove the PCI device, by writing a non-zero
>>> integer to the file. if i remove the device , will the bar resource
>>> map still appear on /proc/iomem ?
>>
>> Of course not.
>>
>>>
>>>
>>> -Ratheesh
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>
>>
>> --
>> Thanks!
>> Yijing
>>
>
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2014-12-17 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 17:51 sysfs-pci remove ratheesh kannoth
2014-12-17 1:00 ` Yijing Wang
2014-12-17 5:21 ` ratheesh kannoth
2014-12-17 5:50 ` Yijing Wang [this message]
2014-12-17 6:08 ` ratheesh kannoth
2014-12-17 6:14 ` Yijing Wang
2014-12-17 6:21 ` ratheesh kannoth
2014-12-17 7:36 ` Yijing Wang
2014-12-17 19:09 ` Bjorn Helgaas
2014-12-18 1:03 ` Yijing Wang
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=549119A9.4010406@huawei.com \
--to=wangyijing@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=ratheesh.ksz@gmail.com \
/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.