Re: Now that the meltdown-patches are in STABLE...

[Eugene Grosbein]

27.02.2018 5:47, Konstantin Belousov wrote:

> I put the snapshot of the WIP of the merge to 11.1 at
> https://kib.kiev.ua/kib/amd64_11.1_meltdown.1.patch
> 
> I only compiled this on the stable/11, not even booted.  I suspect that
> it is not compilable on 11.1 because apparently the patch depends on some
> features of assembler only added in clang 5.0.
> 
> If somebody does the runtime test of the patch, it would be useful.

I've just used 10.4-STABLE r329879 running inside VirtualBox 5.2.2
to build releng/11.1 r330038 plus this patch. Had to manually fix
single reject due to $FreeBSD$ mismatch in the sys/amd64/include/frame.h.rej

Otherwise, it builds just fine. And booted, too.

Not sure if there are other runtime tests needed.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Now that the meltdown-patches are in STABLE...

[Tim Daneliuk]

On 02/26/2018 02:47 PM, Rainer Duffner wrote:
> Am I right to assume they aren’t being backported to 11.1 and we have to wait 
> for 11.2?
> 
> 
> Don’t get me wrong - I’d rather have a stable system when random reboots 
> during the daily or weekly runs.
> 
> But for my own planing, I’d really like to know what the way forward is going 
> to look like.
> 
> 
> https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities
> 
> Isn’t too helpful in this matter.

Ditto for 10.x - will these patches ever be backported there?

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Now that the meltdown-patches are in STABLE...

[Konstantin Belousov]

On Mon, Feb 26, 2018 at 09:47:26PM +0100, Rainer Duffner wrote:
> Am I right to assume they aren???t being backported to 11.1 and we have to 
> wait for 11.2?
> 
> 
> Don???t get me wrong - I???d rather have a stable system when random reboots 
> during the daily or weekly runs.
> 
> But for my own planing, I???d really like to know what the way forward is 
> going to look like.
> 
> 
> https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities
> 
> Isn???t too helpful in this matter.

I put the snapshot of the WIP of the merge to 11.1 at
https://kib.kiev.ua/kib/amd64_11.1_meltdown.1.patch

I only compiled this on the stable/11, not even booted.  I suspect that
it is not compilable on 11.1 because apparently the patch depends on some
features of assembler only added in clang 5.0.

If somebody does the runtime test of the patch, it would be useful.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [HEADS UP] - OFED/RDMA stack update

[Konstantin Belousov]

On Mon, Feb 26, 2018 at 02:21:39PM -0800, Navdeep Parhar wrote:
> +freebsd-arch@
> 
> Hi Meny,
> 
> Can you please post the KPI/KBI analysis that you generated to some
> public location and provide a link here?  A straight MFC would be a
> major break of KPI/KBI in -STABLE and the options we're looking at are:
I put the report at
https://kib.kiev.ua/kib/ibcore_11_to_11_merged_compat_report.html

> 
> a) Ignore the breakage and let downstream consumers deal with the
> fallout.  This obviously isn't ideal in a -STABLE branch.
> 
> b) Provide compat shims to at least preserve the KPI.  One challenge is
> that the changes include functions with the same name but different
> signature/behavior.  See, for example, ib_create_cq in Meny's list once
> he publishes it.
Project did handled similar issues already.  One of the approaches is to
renname the ib_create_cq with the new signature to ib_create_cq_n12 and
check for (e.g.) _WANT_NEW_OFED symbol and to select one or another:
#ifdef _WANT_NEW_OFED
#define ib_create_cq(new args there) ib_create_cq_n21(new args there)
#else
#define ib_create_cq (ib_create_cq)
#endif

Then ULP that wants new KPI defines _WANT_NEW_OFED.

> 
> c) Have two versions of the OFED interfaces in 11-STABLE and not break
> existing downstream consumers at all.
It is possible to make them loadable simultaneously as modules, but it
is quite confusing to users, because Mellanox clearly wants mlx5_ib and
mlx4_ib to work only with new OFED, while cxgbe would use old OFED ?

Also, either we would need to mess with the ibcore.ko module name, or
with version.  I am not sure that our module handling is robust enough
to make the version trick possible.

> 
> I've reached out to users that I know of and know will be affected.
> If you use OFED and FreeBSD 11 this would be a good time to weigh
> in with your thoughts, ideas, concerns etc..
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [HEADS UP] - OFED/RDMA stack update

[Navdeep Parhar]

+freebsd-arch@

Hi Meny,

Can you please post the KPI/KBI analysis that you generated to some
public location and provide a link here?  A straight MFC would be a
major break of KPI/KBI in -STABLE and the options we're looking at are:

a) Ignore the breakage and let downstream consumers deal with the
fallout.  This obviously isn't ideal in a -STABLE branch.

b) Provide compat shims to at least preserve the KPI.  One challenge is
that the changes include functions with the same name but different
signature/behavior.  See, for example, ib_create_cq in Meny's list once
he publishes it.

c) Have two versions of the OFED interfaces in 11-STABLE and not break
existing downstream consumers at all.

I've reached out to users that I know of and know will be affected.
If you use OFED and FreeBSD 11 this would be a good time to weigh
in with your thoughts, ideas, concerns etc..

Regards,
Navdeep

On Mon, 2018-02-26 at 14:49 +, Meny Yossefi wrote:
> Hi, 
> 
> We are currently working on MFC'ing the OFED/RDMA stack update
> mentioned below to FreeBSD11-STABLE.
> 
> We already have working version in 'projects/bsd_rdma_4_9_stable_11'
> (pending iWARP updates) and currently working on ULP integration.
> 
> Again, as always, for any concern/comments you might have, please
> don't hesitate contacting us.
> 
> freebsd-driv...@mellanox.com
> 
> 
> Regards, 
> 
> Meny Yossefi, 
> Mellanox technologies
> 
> 
> -Original Message-
> From: Meny Yossefi 
> Sent: Monday, November 13, 2017 11:09 AM
> To: 'freebsd-infinib...@freebsd.org' ;
> 'freebsd-curr...@freebsd.org' 
> Cc: freebsd-drivers 
> Subject: [HEADS UP] - OFED/RDMA stack update 
> 
> Hi, 
> 
> This is to inform you that by end of this week we plan to merge the
> OFED/RDMA stack update from the project - 'bsd_rdma_4_9' into 12-
> CURRENT.
> The update aligns the OFED common code and RDMA vendor drivers with
> Linux v4.9.
> 
> We are still working on final modifications and build testing it prior
> to submission.
> 
> 
> For any concern/comments you might have, please don't hesitate
> contacting us.
> 
> freebsd-driv...@mellanox.com
> 
> 
> Regards, 
> 
> Meny Yossefi, 
> Mellanox technologies
> ___
> freebsd-infinib...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-infiniband
> To unsubscribe, send any mail to "freebsd-infiniband-unsubscribe@freeb
> sd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Now that the meltdown-patches are in STABLE...

[Rainer Duffner]

Am I right to assume they aren’t being backported to 11.1 and we have to wait 
for 11.2?


Don’t get me wrong - I’d rather have a stable system when random reboots during 
the daily or weekly runs.

But for my own planing, I’d really like to know what the way forward is going 
to look like.


https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities

Isn’t too helpful in this matter.




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

[Ronald Klop]

On Sun, 25 Feb 2018 16:48:44 +0100, Johannes M Dieterich   
wrote:



Dear all,

Please CC me as I am not subscribed.

On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.

We have tested this on a range of hardware ourselves:
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris

Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
patches, please do so at our development github:

https://github.com/FreeBSDDesktop/kms-drm

We absolutely do welcome contributions!

Johannes



Nice work. It might be nice to edit the linux 4,9 reference from pkg-descr.

Regards,
Ronald.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

[Pete Wright]

On 2/25/18 7:48 AM, Johannes M Dieterich wrote:
> Dear all,
>
> Please CC me as I am not subscribed.
>
> On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
> of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
> report that the graphics/drm-next-kmod port just received an update to
> Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
> CURRENT and 11-STABLE.
>
> We have tested this on a range of hardware ourselves:
> * Haswell
> * Broadwell
> * Skylake
> * Evergreen
> * Kaveri (both radeon and amgpu KMS)
> * Carrizo
> * Polaris
>
> Needless to say, the possible space of hardware this could run on is
> significantly larger. Hence, if you find issues and/or want to propose
> patches, please do so at our development github:
>
> https://github.com/FreeBSDDesktop/kms-drm
>
> We absolutely do welcome contributions!

Thanks JMD and everyone who hacked on this the past couple days.  I can
confirm that this works as expected on my 11-STABLE with a Kabylake CPU,
so we can add that hardware to the list above :)


Cheers,
-pete

-- 
Pete Wright
p...@nomadlogic.org
310.309.9298

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

RE: [HEADS UP] - OFED/RDMA stack update

[Meny Yossefi]

Hi, 

We are currently working on MFC'ing the OFED/RDMA stack update mentioned below 
to FreeBSD11-STABLE.

We already have working version in 'projects/bsd_rdma_4_9_stable_11' (pending 
iWARP updates) and currently working on ULP integration.

Again, as always, for any concern/comments you might have, please don't 
hesitate contacting us.

freebsd-driv...@mellanox.com


Regards, 

Meny Yossefi, 
Mellanox technologies


-Original Message-
From: Meny Yossefi 
Sent: Monday, November 13, 2017 11:09 AM
To: 'freebsd-infinib...@freebsd.org' ; 
'freebsd-curr...@freebsd.org' 
Cc: freebsd-drivers 
Subject: [HEADS UP] - OFED/RDMA stack update 

Hi, 

This is to inform you that by end of this week we plan to merge the OFED/RDMA 
stack update from the project - 'bsd_rdma_4_9' into 12-CURRENT.
The update aligns the OFED common code and RDMA vendor drivers with Linux v4.9.

We are still working on final modifications and build testing it prior to 
submission.


For any concern/comments you might have, please don't hesitate contacting us.

freebsd-driv...@mellanox.com


Regards, 

Meny Yossefi, 
Mellanox technologies
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"