From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
kernel list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: iommu breaks usb after resume
Date: Thu, 27 Mar 2008 21:30:37 +0100 [thread overview]
Message-ID: <200803272130.38375.rjw@sisk.pl> (raw)
In-Reply-To: <20080326225407.GA9378@elf.ucw.cz>
On Wednesday, 26 of March 2008, Pavel Machek wrote:
> Hi!
>
> > > CONFIG_AGP=y
> > > CONFIG_AGP_AMD64=y
> > > CONFIG_AGP_INTEL=y
> > > # CONFIG_AGP_SIS is not set
> > > CONFIG_AGP_VIA=y
> > > CONFIG_DRM=y
> > > # CONFIG_DRM_TDFX is not set
> > >
> > > ...do I need to enable something more?
> >
> > Should have worked then. Ok modulo bugs. Maybe the ordering
> > is wrong now (AGP resume would need to run before anything
> > using the IOMMU)
>
> So agp_amd64_resume() is responsible for reiniting iommu on new amd64
> boxes?
>
> It is registered as normal pci driver:
>
> static struct pci_driver agp_amd64_pci_driver = {
> .name = "agpgart-amd64",
> .id_table = agp_amd64_pci_table,
> .probe = agp_amd64_probe,
> .remove = agp_amd64_remove,
> #ifdef CONFIG_PM
> .suspend = agp_amd64_suspend,
> .resume = agp_amd64_resume,
> #endif
> };
>
> ...should it be modified to run early, as other pci devices (USB
> controllers) may rely on this?
>
> I did this... I'll verify it in 10 hours or so. If someone has amd64
> system with >=4G ram, there should be hibernation problems. This
> should fix it:
>
> diff --git a/drivers/char/agp/amd64-agp.c b/drivers/char/agp/amd64-agp.c
> index d8200ac..4e85178 100644
> --- a/drivers/char/agp/amd64-agp.c
> +++ b/drivers/char/agp/amd64-agp.c
> @@ -594,12 +594,14 @@ static int agp_amd64_suspend(struct pci_
>
> static int agp_amd64_resume(struct pci_dev *pdev)
> {
> + printk("agp_amd64: resume\n");
> pci_set_power_state(pdev, PCI_D0);
> pci_restore_state(pdev);
>
> if (pdev->vendor == PCI_VENDOR_ID_NVIDIA)
> nforce3_agp_init(pdev);
>
> + printk("agp_amd64: 8151 configure\n");
> return amd_8151_configure();
> }
>
> @@ -733,8 +735,8 @@ static struct pci_driver agp_amd64_pci_d
> .probe = agp_amd64_probe,
> .remove = agp_amd64_remove,
> #ifdef CONFIG_PM
> - .suspend = agp_amd64_suspend,
> - .resume = agp_amd64_resume,
> + .suspend_late = agp_amd64_suspend,
> + .resume_early = agp_amd64_resume,
> #endif
> };
Okay, a couple of questions:
(1) Are you sure that the .suspend() and .resume() callbacks will just work
with interrupts disabled?
(2) Even if they work, is it sufficient to just move them to the "late" and
"early" parts? That is, isn't there anything using the iommu in the
"early" and "late" callbacks of the other devices?
Rafael
next prev parent reply other threads:[~2008-03-27 20:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 11:14 iommu breaks usb after resume Pavel Machek
2008-03-21 13:27 ` Ingo Molnar
2008-03-21 13:54 ` Andi Kleen
2008-03-26 10:21 ` Pavel Machek
2008-03-26 13:00 ` Andi Kleen
2008-03-26 22:54 ` Pavel Machek
2008-03-26 23:00 ` Ingo Molnar
2008-03-26 23:05 ` Pavel Machek
2008-03-27 5:53 ` Andi Kleen
2008-03-27 8:41 ` Pavel Machek
2008-03-27 8:42 ` Pavel Machek
2008-03-27 8:47 ` (eats disks) " Pavel Machek
2008-03-27 9:59 ` Pavel Machek
2008-03-27 11:49 ` Andi Kleen
2008-03-27 13:29 ` Pavel Machek
2008-03-27 13:34 ` Andi Kleen
2008-03-27 20:30 ` Rafael J. Wysocki [this message]
2008-03-27 23:40 ` Pavel Machek
2008-03-27 23:52 ` Rafael J. Wysocki
2008-03-28 13:50 ` Pavel Machek
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=200803272130.38375.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
/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