[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <EE124450C0AAF944A40DD71E61F878C98FBD6A@SINEX14MBXC417.southpacific.corp.microsoft.com>
Date: Fri, 1 Aug 2014 10:22:53 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Tomi Valkeinen <tomi.valkeinen@...com>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"dan.carpenter@...cle.com" <dan.carpenter@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"driverdev-devel@...uxdriverproject.org"
<driverdev-devel@...uxdriverproject.org>,
"plagnioj@...osoft.com" <plagnioj@...osoft.com>,
"linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: [PATCH v3] video: hyperv: hyperv_fb: refresh the VM screen by
force on VM panic
> -----Original Message-----
> From: Tomi Valkeinen [mailto:tomi.valkeinen@...com]
> Sent: Thursday, July 31, 2014 21:38 PM
> > I think in hvfb_on_panic() we should be able to get the
> > hvfb_info pointer by
> > hvfb_info = container_of(nb, struct hv_fb_panic_nb, nb).
> >
> > If you like that or have a better idea, please let me know so
> > I can make a new patch.
>
> Or maybe you can add the notifier_block and the synchronous_fb to
> hvfb_par? From the notifier_block pointer you could then get hvfp_par,
> and from there hvfb_info.
> Tomi
Hi Tomi,
Thanks a lot for the suggestion! It's better.
I'll send out a v4 patch for your review.
Thanks,
-- Dexuan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists