From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: paulus@samba.org, nfont@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/pseries: Check if EEH is enabled on DDW mechanism code
Date: Wed, 3 Feb 2016 10:26:36 -0200 [thread overview]
Message-ID: <56B1F1FC.1080403@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160202234811.GA17911@gwshan>
On 02/02/2016 09:48 PM, Gavin Shan wrote:
> On Tue, Jan 19, 2016 at 06:18:20PM -0200, Guilherme G. Piccoli wrote:
>> - /* only attempt to use a new window if 64-bit DMA is requested */
>> - if (!disable_ddw && dma_mask == DMA_BIT_MASK(64)) {
>> + /* We should check if EEH is enabled here, since DDW mechanism has
>> + * an intrinsic dependency of EEH config addr information. Also, we
>> + * only attempt to use a new window if 64-bit DMA is requested */
>> + if (eeh_enabled() && !disable_ddw && dma_mask == DMA_BIT_MASK(64)) {
>> dn = pci_device_to_OF_node(pdev);
>> dev_dbg(dev, "node is %s\n", dn->full_name);
>>
>
> There are two types of addresses: (1) PCI config address (2) PE config address.
> (1) is used to indentify one PCI device which is included in the PE. (2) is the
> PCI config address of PE's primary bus in pHyp. Both of them can be used to identify
> the PE. It means the (1) PCI config address, which is retrieved from pci_dn, can be
> passed to hypervisor. Then we don't have to disable DDW when EEH is disabled.
>
> Guilherme, did you hit the crash on pHyp or PowerKVM?
Gavin, thanks very much for the clarification. So, we can interchange
edev->config_addr with pdn->pci_ext_config_space ?
This would solve the issue with DDW being enabled when EEH is not.
I hit the issue on PowerVM (PHyp). I wasn't able to perform hotplug in
qemu that time I was testing this - I can re-test on qemu. Can we use
pci_dn config address in qemu guest too?
Cheers,
Guilherme
next prev parent reply other threads:[~2016-02-03 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 20:18 [PATCH 0/2] Two patches regarding EEH availability checks - DLPAR/DDW Guilherme G. Piccoli
2016-01-19 20:18 ` [PATCH 1/2] powerpc/eeh: Check for EEH availability in eeh_add_device_early() Guilherme G. Piccoli
2016-02-02 22:44 ` Gavin Shan
2016-02-03 11:54 ` Guilherme G. Piccoli
2016-02-04 5:27 ` Gavin Shan
2016-01-19 20:18 ` [PATCH 2/2] powerpc/pseries: Check if EEH is enabled on DDW mechanism code Guilherme G. Piccoli
2016-02-02 23:48 ` Gavin Shan
2016-02-03 12:26 ` Guilherme G. Piccoli [this message]
2016-02-04 5:30 ` Gavin Shan
2016-04-07 0:23 ` Guilherme G. Piccoli
2016-02-01 12:47 ` [PATCH 0/2] Two patches regarding EEH availability checks - DLPAR/DDW Guilherme G. Piccoli
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=56B1F1FC.1080403@linux.vnet.ibm.com \
--to=gpiccoli@linux.vnet.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.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 NNTP newsgroup(s).