[Valgrind-developers] Valgrind repository access and AVX-512 development progress

Discussion:

Mineeva, Tatyana A

2017-03-29 15:54:22 UTC

Hello Julian and Valgrind developers,
I'm working with the Intel team to add AVX-512 support to Valgrind.

Our team cannot access the Valgrind Subversion repository:
$ svn co svn://svn.valgrind.org/valgrind/trunk valgrind
svn: Can't connect to host 'svn.valgrind.org': Connection timed out
Is the this repository functional, or should we switch to the git repository?

We do not currently have success cloning the Valgrind git repository:
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
fatal: unable to connect to sourceware.org:
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

Might you or another developer have an idea of configuration settings we should use on our end?

I would also like to take this opportunity to update you on our current progress on adding AVX-512 support to Valgrind. We will appreciate any comments and questions.
We started with the base Valgrind 3.12.0 which we downloaded from the website.
- Extended Valgrind's HW capabilities detection to detect AVX-512 support and tell VEX about it.
- Extended the implementation of XSAVE and XRSTOR to cover the new registers. We tested it under Nulgrind on the tests from ./memcheck/tests/amd64/xsave-avx.c, which we extended to cover the new register state. We haven't yet tested it on a real context switch or runtime library call.
- Added support of a few AVX-512 instructions (vmovups, vmovdqa32, vmovdqa64, vpsubd) to Valgrind core. The instructions double up the IR of their AVX-2 version.
- For the tests, we are using a slightly modified version of none/tests/amd64/avx2-1.c. Basically, it replaces ymm registers with zmm registers; it does not verify the new features of AVX-512 instructions (such as opmasks) yet. The newly added instructions pass the tests under Nulgrind.
- We are currently adding support of the new registers to memcheck.
We plan to try implementing some AVX-512 instructions without doubling up the existing IR next.

Best regards,
Tanya

--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Eliot Moss

2017-03-29 16:02:42 UTC

Permalink

Post by Mineeva, Tatyana A
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

Dear Mineeva -- Of course it could be a corporate firewall or something,
but I have sometimes found that using http:/https: vs git: can make a
difference when checking out a public repository. I just tried the git:
from Cygwin on my Windows 10 box and it cloned just fine. This makes me
suspect a networking issue particular to you, or that there was a short-
term connectivity issue.

Regards - Eliot Moss

Julian Seward

2017-03-29 16:21:44 UTC

Permalink

Post by Mineeva, Tatyana A
$ svn co svn://svn.valgrind.org/valgrind/trunk valgrind
svn: Can't connect to host 'svn.valgrind.org': Connection timed out
Is the this repository functional, or should we switch to the git repository?

The SVN repo works fine. I've been using it this afternoon and committed
to it just a few minutes ago. So as Eliot says, this is probably a
corporate firewall problem. Such things have happened before.

Post by Mineeva, Tatyana A
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

I don't know. Ivo might know more. Ivo?

Post by Mineeva, Tatyana A
I would also like to take this opportunity to update you on our current
progress on adding AVX-512 support to Valgrind.

Thank you for the update. That sounds promising. I suspect there will
be some fun and games merging this with the trunk, so in general it would
be best if you can keep your work based on the most recent possible version
of the trunk, rather than on 3.12.0.

J

Ivo Raisr

2017-03-29 21:29:33 UTC

Permalink

Post by Julian Seward

Indeed, corporate proxy problem.
Unfortunately svn.valgrind.org does not offer access via http:// (which would
allow to specify http proxy at hand).
So in our corporate settings, I ended up with a horrible hack using
'socat' tunneling.
I can share details if you are interested.

Post by Julian Seward

Post by Mineeva, Tatyana A
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

I don't know. Ivo might know more. Ivo?

Knapp, Rashawn L

2017-03-29 21:40:54 UTC

Permalink

Thank you everyone who offered svn and git access help. For now, we have resolved the git clone issue; we will tackle the svn checkout late. We did need to contact corporate system administrators and we were able to resolve our git clone issue using, as Ivo suggests, socat and configuration file creations which identify the correct proxy server and protocol. The difficult part was that this was not straightforward for us as the process on our end was different this time for this public git repo.

Regards,

-Rashawn
-----Original Message-----
From: Ivo Raisr [mailto:***@ivosh.net]
Sent: Wednesday, March 29, 2017 2:30 PM
To: Mineeva, Tatyana A <***@intel.com>
Cc: valgrind-***@lists.sourceforge.net
Subject: Re: [Valgrind-developers] Valgrind repository access and AVX-512 development progress

Post by Julian Seward

The SVN repo works fine. I've been using it this afternoon and
committed to it just a few minutes ago. So as Eliot says, this is
probably a corporate firewall problem. Such things have happened before.

Indeed, corporate proxy problem.
Unfortunately svn.valgrind.org does not offer access via http:// (which would allow to specify http proxy at hand).
So in our corporate settings, I ended up with a horrible hack using 'socat' tunneling.
I can share details if you are interested.

Post by Julian Seward

Post by Mineeva, Tatyana A
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

I don't know. Ivo might know more. Ivo?

Mineeva, Tatyana A

2017-05-10 16:13:25 UTC

Permalink

Hello Ivo,

Could you please explain how to connect to Valgrind SVN through 'socat' tunneling?
Also, do I understand correctly that the Git repository does not update along with the svn trunk yet? The latest Git commit I can pull is from March, 4, "Convert release-HOWTO.txt from SVN to GIT".

Regards, Tanya

-----Original Message-----
From: Knapp, Rashawn L
Sent: Thursday, March 30, 2017 12:41 AM
To: Ivo Raisr <***@ivosh.net>; Mineeva, Tatyana A <***@intel.com>
Cc: valgrind-***@lists.sourceforge.net
Subject: RE: [Valgrind-developers] Valgrind repository access and AVX-512 development progress

Thank you everyone who offered svn and git access help. For now, we have resolved the git clone issue; we will tackle the svn checkout late. We did need to contact corporate system administrators and we were able to resolve our git clone issue using, as Ivo suggests, socat and configuration file creations which identify the correct proxy server and protocol. The difficult part was that this was not straightforward for us as the process on our end was different this time for this public git repo.

Regards,

-Rashawn
-----Original Message-----
From: Ivo Raisr [mailto:***@ivosh.net]
Sent: Wednesday, March 29, 2017 2:30 PM
To: Mineeva, Tatyana A <***@intel.com>
Cc: valgrind-***@lists.sourceforge.net
Subject: Re: [Valgrind-developers] Valgrind repository access and AVX-512 development progress

Post by Julian Seward

The SVN repo works fine. I've been using it this afternoon and
committed to it just a few minutes ago. So as Eliot says, this is
probably a corporate firewall problem. Such things have happened before.

Indeed, corporate proxy problem.
Unfortunately svn.valgrind.org does not offer access via http:// (which would allow to specify http proxy at hand).
So in our corporate settings, I ended up with a horrible hack using 'socat' tunneling.
I can share details if you are interested.

Post by Julian Seward

Post by Mineeva, Tatyana A
$ git clone git://sourceware.org/git/valgrind.git
Cloning into 'valgrind'...
sourceware.org[0: 209.132.180.131]: errno=Connection timed out

I don't know. Ivo might know more. Ivo?

Two commets here:
1) valgrind.git at sourceware.org is still unofficial, testing repo.
And it will remain so until
migration from SVN to GIT happens, which is bound after 3.13 release is done.
2) Again, your corporate firewall is blocking access here.

I.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
Valgrind-developers mailing list
Valgrind-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-developers

--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Ivo Raisr

2017-05-11 08:50:51 UTC

Permalink

Post by Mineeva, Tatyana A
Hello Ivo,
Could you please explain how to connect to Valgrind SVN through 'socat' tunneling?

Sure. The magic incantation is:

socat TCP4-LISTEN:3690,reuseaddr,fork
"PROXY:<your-proxy-servername-here>:svn.valgrind.org:3690,proxyport=<your-proxy-port-here>"
&

Then do something along these lines:
svn co --ignore-externals "svn://localhost:3690/valgrind/trunk" valgrind
svn co --ignore-externals "svn://localhost:3690/vex/trunk" valgrind/VEX

Post by Mineeva, Tatyana A
Also, do I understand correctly that the Git repository does not update along with the svn trunk yet?

It is currently for testing only. I'll update it with the latest SVN
commits tomorrow.

I.